-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Cloud Posture] Ensure package policy namespace is always set to default #152168
Conversation
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 a bunch of mentions of 'default'
, would be better to have one shared constant for that value
7e2b1e0
to
f6a462d
Compare
💚 Build Succeeded
Metrics [docs]Async chunks
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…o default (#152168) (#152175) # Backport This will backport the following commits from `main` to `8.7`: - [[Cloud Posture] Ensure package policy namespace is always set to default (#152168)](#152168) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Or Ouziel","email":"or.ouziel@elastic.co"},"sourceCommit":{"committedDate":"2023-02-27T05:26:14Z","message":"[Cloud Posture] Ensure package policy namespace is always set to default (#152168)","sha":"5d3d75fe83aa662d3b7d1acad282ab7a55fbce06","branchLabelMapping":{"^v8.8.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","v8.7.0","v8.8.0"],"number":152168,"url":"https://github.com/elastic/kibana/pull/152168","mergeCommit":{"message":"[Cloud Posture] Ensure package policy namespace is always set to default (#152168)","sha":"5d3d75fe83aa662d3b7d1acad282ab7a55fbce06"}},"sourceBranch":"main","suggestedTargetBranches":["8.7"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.8.0","labelRegex":"^v8.8.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/152168","number":152168,"mergeCommit":{"message":"[Cloud Posture] Ensure package policy namespace is always set to default (#152168)","sha":"5d3d75fe83aa662d3b7d1acad282ab7a55fbce06"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Summary
once #151886 is merged, changes to agent policy will update the package policy id and also the namespace. in our case, we only support the
default
namespace (IIRC - to prevent confusion with k8s namespaces)so this PR adds an effect to ensure the namespace is always set to default