-
Notifications
You must be signed in to change notification settings - Fork 15
Ensure RabbitMQ Broker reaches synced status when using non-default security group #104
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
base: main
Are you sure you want to change the base?
Ensure RabbitMQ Broker reaches synced status when using non-default security group #104
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: knottnt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all |
1 similar comment
/test all |
- Add .vscode to .gitignore - Enable late_initialize for fields not set by the Create API's response - Set omit_unchanged_fields to true - Set only_set_unchanged_fields to true
- Add custom hook to check that latest EngineVersion has Spec.EngineVersion as prefix instead of checking for exact match.
- Add e2e test to ensure that the ACK resource syncs when creating a RabbitMQ broker with a non-default security group
- Move creation of broker to fixture - Add test logic for validating update of broker
/test mq-kind-e2e |
7dcabd0
to
402a132
Compare
/test all |
/hold |
- method: Update | ||
ignore: true | ||
MaintenanceWindowStartTime: | ||
late_initialize: {} |
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.
should we add a late_initialize_all
field at the Resource level in code-gen?
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.
Hmm, that could be useful. Not sure if I want to block this PR on that code-gen feature though.
# UpdateBroker API returns nil for values not set in the request. | ||
only_set_unchanged_fields: true |
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.
should we consider ignoring the update output completely? and do late_initialize only?
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.
Hmm, the update output does have relevant information, but only for the fields that were non-nil in the input shape. What would the benefit of relying on late_initialize only? Also, for late_initialization don't we only set nil fields? The fields in the delta will already be set so the updated values won't be reflected.
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.
I was thinking late_initialize
would just patch all the necessary updated fields from AWS.
If the response you get from update output is the same as the update input, i don't think we need to set those fields again..
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.
There are some cases where we AWS does slightly modify the input value in the output that we want to pick-up to avoid errant drift detection. For example if you send a maintenance window day of "Monday" the Update operation will return MONDAY. We could try catching all of those cases in the delta function, but that would require quite a bit of custom code.
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.
that makes sense
- Add test case for delta when engine version differs by patch version
@knottnt: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/unhold |
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.