-
Notifications
You must be signed in to change notification settings - Fork 398
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
fix assert of deploymentCircuitBreaker #1217
fix assert of deploymentCircuitBreaker #1217
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
recheck |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run tests locally and they now pass. I'd missed that they didn't run last time.
Wow woops thanks for cleaning this up! Doesn't the PR pipeline run the integration tests? Was there a way for me to tell that it was failing? |
ATM not. But work for it is in progress.
basically you're place the
afterwards you can run
but somewhere must be also a more detailed manual for it. |
backport-3: ecs_service deployment_circuit_breaker SUMMARY manual backport of #1215 #1217 there is no version_added, because the module already supports this feature. it was just undocumented. ISSUE TYPE Bugfix Pull Request Docs Pull Request Feature Pull Request COMPONENT NAME ecs_service ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None>
backport-2: ecs_service deployment_circuit_breaker SUMMARY manual backport of #1215 #1217 there is no version_added, because the module already supports this feature. it was just undocumented. ISSUE TYPE Bugfix Pull Request Docs Pull Request Feature Pull Request COMPONENT NAME ecs_service ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None>
SUMMARY
fix broken ecs_cluster integration test of #1215
cc @tremble @karcadia
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION