Skip to content
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

Backport of Fix duplicate key in connect-inject ACL policy into release/1.5.x #4436

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #4434 to be assessed for backporting due to the inclusion of the label backport/1.5.x.

The below text is copied from the body of the original PR.


Changes proposed in this PR

Stop including a duplicate acl = "write" rule at the root level of the connect-inject ACL policy when namespaces are not enabled. The security patch in hashicorp/consul#21908 led to the connect-injector being unable to start up as its ACL policy is rejected by Consul.

How I've tested this PR

  1. Expanded the test matrix to cover all possible flag combinations w/ current policy output
  2. Fixed policy generation
  3. Updated the test assertions to account for the bug fix, verifying that acl = "write" never appears twice at the root level of the policy with any combination of flags

How I expect reviewers to test this PR

Review commit-by-commit observing the above

Checklist


Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core merged commit f5b0a9f into release/1.5.x Nov 28, 2024
48 of 49 checks passed
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/fix-duplicate-key-in-acl-policy/deadly-helpful-honeybee branch November 28, 2024 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants