jlindgre@redhat.com to make this ticket not complete junk

The superkey worker does the creation so that will have to get updated to handle adding that external-id to the role.

—

HELLO

Lets get some requirements on this bad boy. So it looks like cost-management wants to use external-id's on their roles. It looks like that would just be a change in a few places. 

1. The UI will have to pass the external-id from the form, or we'd generate it. Up to cost-management. Maybe either/or with the backend looking for "generate" or some magic string that means generate it. Would have to live on the superkey authentication object OR the application object.
2. The superkey metadata seed file will have to be updated to include that new field with probably a new substitution: https://github.com/RedHatInsights/sources-api-go/blob/0899b85d5c3b0fb91d3401a7ed12c5889e1b598a/dao/seeds/superkey_metadata.yml#L62-L79
3. The worker will just have to have yet another replacement here, replacing the external-id (if the substitution exists) with the one from the payload or generated: https://github.com/RedHatInsights/sources-superkey-worker/blob/ce93818c652d105fa95d34585e6a14b193a91d66/provider/amazon_provider.go#L102
4. When posting the new authentication back - it will have to include the external id in the auth payload. 

Happy to delve deeper - but those are the steps it would take to do this.