Update Cloud Defend integration to include beta release tag
#10541
Conversation
💔 Build Failed
Failed CI StepsHistory |
andrewkroh
added
Integration:cloud_defend
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
There was a problem hiding this comment.
Through the use of semver in the version field is only way to indicate that a release is considered "pre-release" (e.g. alpha, beta).
But this will not undo the fact that there are earlier releases without the "beta" pre-release indicator present in the Elastic Package Registry (EPR). The side-effect is that Fleet will not display this new "beta" release by default (unless you toggle Display beta integrations). And it will continue to suggest that there is a GA version like in this screenshot.
| @@ -10,6 +10,7 @@ categories: | |||
| - containers | |||
| - kubernetes | |||
| - security | |||
| release: beta | |||
There was a problem hiding this comment.
This tag is no longer supported. See elastic/kibana#122973.
andrewkroh
added
bugfix
|
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
This PR resolves elastic/security-docs#5583 and adds the
betatag to the Cloud Defend integration. I'm not sure how to test this to ensure the changes appear as they should before merging; can someone help with that?