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

[BUG] Documentation Defend for Cloud doesn't show itself as in beta stage #5583

Closed
111andre111 opened this issue Jul 18, 2024 · 4 comments · May be fixed by elastic/integrations#10541
Closed
Assignees
Labels
bug Something isn't working

Comments

@111andre111
Copy link

111andre111 commented Jul 18, 2024

Documentation links

https://www.elastic.co/docs/current/integrations/all_integrations
https://www.elastic.co/docs/current/integrations/cloud_defend

Description

At the moment Defend for Containers is at beta stage, however this is now reflected in our documentation.
Our serverless documentation has it correctly:
https://www.elastic.co/docs/current/serverless/security/d4c-overview
as well as
https://www.elastic.co/guide/en/security/current/d4c-overview.html

So I think that's because release tag is missing in
https://github.com/elastic/integrations/blob/main/packages/cloud_defend/manifest.yml

similar to e,g, this integration:
https://github.com/elastic/integrations/blob/main/packages/linux/manifest.yml#L10

Which documentation set(s) does this bug apply to?

ESS and serverless

Release version

No response

Testing environment

At the end on both pages integration should show in beta stage

@111andre111 111andre111 added the bug Something isn't working label Jul 18, 2024
@111andre111 111andre111 changed the title [BUG] [BUG] Dkch Jul 18, 2024
@111andre111 111andre111 changed the title [BUG] Dkch [BUG] Documentation Defend for Cloud doesn't show itself as in beta stage Jul 18, 2024
@jmikell821 jmikell821 self-assigned this Jul 19, 2024
@jmikell821
Copy link
Contributor

@111andre111 - I opened elastic/integrations#10541. Can you review please?

@jrmolin
Copy link

jrmolin commented Jul 22, 2024

@111andre111 I'm not sure that adding release: beta is the correct response, given the documentation in elastic-package that identifies the release property as an unsupported (but common) one. Ref: https://github.com/elastic/elastic-package/blob/09d372c994f47d12528977a7788f0e313112f84b/docs/howto/update_major_package_spec.md?plain=1#L160-L171

That blob is useful for explaining why the very simple PR is failing linting, but not how to resolve it cleanly.

@111andre111
Copy link
Author

111andre111 commented Jul 28, 2024

Ah, ok, so I learnt from the linked kibana issue elastic/kibana#122973 that rather not the release tag, but rather the version tag moving it from 1.2.5 to 1.2.6-beta would make it beta. Was not aware of that change...

If that basically changed under the hood that would mean that rather an inventory needs to be done because I assume there could be much more integrations that are supposed to be on beta or tech-preview stage but are at GA it seems today because of that change.

@jmikell821
Copy link
Contributor

Closing this; consulted with the Integrations team and the release tag is no longer supported. Details in Slack thread here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants