fix(networkacl): Correct update order and entries/associations handlers #202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The custom update logic for
NetworkACL
resources was syncing theEntries
beforethe
Tags
. This could lead to issues if theEntries
sync failed as the Tagswould not be updated..
This change also updates the order to sync
Tags
beforeEntries
. It also usesDeepCopy
when passing the resource tocreateAssociation
and `createEntriesto avoid modifying the original desired state.
Additionally, the exit functions in
hooks.go
were fixed to properlyhandle the error return value.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.