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

Work around eventual consistency in the AWS API #39

Open
rmc3 opened this issue Jun 5, 2018 · 2 comments
Open

Work around eventual consistency in the AWS API #39

rmc3 opened this issue Jun 5, 2018 · 2 comments
Labels
enhancement New feature or request Stretch

Comments

@rmc3
Copy link
Contributor

rmc3 commented Jun 5, 2018

e.g. replace the time.sleep() in Organization convergence methods with something more robust such as polling the AWS API to ensure that newly created entities are shown before proceeding

@rmc3 rmc3 added the enhancement New feature or request label Jun 5, 2018
@rmc3 rmc3 added this to To do in cumulogenesis Jun 5, 2018
@rmc3 rmc3 moved this from To do to Ready for Implementation in cumulogenesis Jun 5, 2018
@ghost
Copy link

ghost commented Jun 11, 2018

I looked into this. There's no waiters in the organizations SDK. Implementing our own would be a larger effort than I think is worth at this point. I'd vote this card become a stretch goal or something if the current implementation is satisfactory.

@rmc3 rmc3 added the Stretch label Jun 11, 2018
@rmc3
Copy link
Contributor Author

rmc3 commented Jun 11, 2018

Agreed.

@rmc3 rmc3 removed this from Ready for implementation in cumulogenesis Jun 11, 2018
@rmc3 rmc3 added this to To do in cumulogenesis Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stretch
Projects
cumulogenesis
  
To do
Development

No branches or pull requests

1 participant