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

[Change Proposal] Add new field for dependency on stack capabilities #560

Closed
jsoriano opened this issue Jul 4, 2023 · 0 comments · Fixed by #561
Closed

[Change Proposal] Add new field for dependency on stack capabilities #560

jsoriano opened this issue Jul 4, 2023 · 0 comments · Fixed by #561
Assignees
Labels
discuss Issue needs discussion

Comments

@jsoriano
Copy link
Member

jsoriano commented Jul 4, 2023

There are some packages that are only useful if certain Elastic features are available. Some of these features are not going to be available in all the serverless offerings, according to these configurations. Packages requiring these features are going to need to declare it.

Add a new field for dependencies on stack capabilities. We can try to add them as a new condition:

conditions:
  kibana.version: '^8.10.0'
  elastic.subscription: 'basic'
  elastic.capabilities:
    - apm
    - uptime

But so far we don't have lists in conditions. If this is a problem, we can use comma-separated lists:

  elastic.capabilities: 'apm,uptime'

Or add a completely new field stack_capabilties.

We need to confirm the final list of capabilities, but so far we can start with:

  • apm
  • uptime
  • enterprise_search
  • serverless_search
  • observability
  • logs_ui
  • serverless (TBD, for packages intended only for serverless)
  • ilm/dlm (TBD, only if there are packages that only work with one of the lifecycle managers)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issue needs discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant