-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow up to improve how notification-api determines the aws account number #258
Comments
This was feed from Ryan for this review: GSA/ttsnotify-brokerpak-sms#4 It didn't fit into scope for sprint Ibis. |
If I attempt to modify my terraform as recommended by Ryan (adding a caller identity and output), I get the following error message. I have seen this error message before when I tried to add a LifecycleConfiguration to the csv bucket. It seems like somewhere at the boundary between regular AWS and cloud.gov, this problem with GetMetadata is preventing the ability to make some modifications. If it were a permissions issue, maybe we could add GetMetadata in the brokerpak, but this "host is down" message makes it look like it's something else. ╷ The story requires terraform changes so I'm blocked. |
Moving into the backlog for later resolution. |
an idea for an enhancement to address the python side:
You should be able to use caller identity to add the AWS account ID into bind/outputs.tf
The values in outputs.tf get added to the bound service's credentials JSON, so you can parse and use them from within app/cloudfoundry_config.py
The text was updated successfully, but these errors were encountered: