-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Fix GKE not being able to disable Cilium Policies #11810
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 GKE not being able to disable Cilium Policies #11810
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @melinath, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 212 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
Hi @maxi-cit The Magic Modules repository has recently migrated from Ruby to Go. You can view more details about this in our announcement here: hashicorp/terraform-provider-google#19583 (or go/mm-migration-announcement if you are a Googler) This open pull request has likely become incompatible due to most YAML and .erb files converting to Go-compatible files. Our team (Magic Modules repository maintainers) has tooling to automatically convert changes to the new language, and we can prepare a new commit for this pull request that is compatible with the migration. In order to push the new changes to your pull request, we would need to force push the commit to your fork's branch. Our tooling saves a backup branch before converting, so we could rollback or open a new pull request if needed. We would also work with you and the PR reviewer in the event additional changes are needed. You also have the option to update the pull request yourself. You can view updated documentation related to the migration changes. We will take no action until we have your explicit permission to push changes to your fork's branch used for this pull request. Let me or your reviewer know if you have any further questions! |
Thanks @c2thorn, I will update accordingly |
@melinath This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
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.
removing from queue pending updates for go rewrite
Hello @c2thorn could you run the tests please? I check it locally and removing the .erb files should be enough to solve conflicts. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 212 Click here to see the affected service packages
🟢 All tests passed! View the build log |
Fixes: hashicorp/terraform-provider-google#19360
The issue was caused due to the 'omitempty' flag on the 'DesiredEnableCiliumClusterwideNetworkPolicy' attribute on the struct that builds the request on the library end. So I am forcing it to be sent whenever there is a change.
Other fields suffer of the same issue, but I believe this is something that this issues should be treated on a case basis.
Release Note Template for Downstream PRs (will be copied)