-
Notifications
You must be signed in to change notification settings - Fork 52
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
Aws#282 This fixes bug #282 #284
Conversation
Pull Request Test Coverage Report for Build 5425788452
💛 - Coveralls |
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.
can you squash commits into single one please to keep git history clean?
you can do for example:
git reset --soft aws:main
git commit -m ...
This type of approach looks okay for now, but in the long term, each condition type should be dealt separately, and only update the condition when the change is required. This way we can cover different types of statuses as well (addresses #277) |
What type of PR is this? bug
Which issue does this PR fix: #282
What does this PR do / Why do we need it: It fixes bug #282
If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
Testing done on this change: Yes
Automation added to e2e: N/A
Will this PR introduce any new dependencies?: No
Will this break upgrades or downgrades. Has updating a running cluster been tested?: No
Does this PR introduce any user-facing change?: No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.