Skip to content
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

Need Timeouts Implemented against AWS API #99

Open
andyKalman opened this issue Feb 8, 2021 · 1 comment
Open

Need Timeouts Implemented against AWS API #99

andyKalman opened this issue Feb 8, 2021 · 1 comment

Comments

@andyKalman
Copy link

Hello - We are facing challenges with onboarding an AWS account to Dome9. It seems we have a race condition due to the eventual consistency of the AWS API in creating the IAM role for Dome9 to use. The error below insinuates that the role created does not have the permissions yet. This is always confirmed to be the case with an immediate re-try of the TF plan/apply. It is always successful....... We have tried the use of depends_on unsuccessfully. It seems that the lack of timeouts in the provider and the timing of the response back from AWS is preventing this from working cleanly.

Can we implement API timeouts for the provider and/or retries according to the Hashi documentation that speaks to this issue located here??

Error: FAILED: POST, https://api.dome9.com/v2/cloudaccounts, 400, 400 Bad Request, Unable to add cloud account: Your API key is missing the permission: 'ec2:DescribeSecurityGroups'. on .terraform/modules/this.baseline_primary/modules/iam-baseline/dome9.tf line 95, in resource "dome9_cloudaccount_aws" "onboarding": 95: resource "dome9_cloudaccount_aws" "onboarding"

@andyKalman
Copy link
Author

To be specific I'm talking about this function for this specific resource if it wasn't clear and the option to add retries.

func resourceCloudAccountAWS() *schema.Resource {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant