-
Notifications
You must be signed in to change notification settings - Fork 117
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
Refactor profiles to decouple them from stack resources #1140
Conversation
* New `elastic-package profile use` command to select profile to use. * Configuration files are not rewritten on upgrade. * Stack and test runner files are managed by their own providers. * Stack and test runner files are only written when the services are started, and only if they are different. * Stack files are templates now. Same files are used for multiple versions. Runtime configuration can be passed now as data to templates instead of requiring environment variables. * Support for multiple stack providers.
🌐 Coverage report
|
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.
Great refactor! go-resource
lib is quite helpful for this use case 👍
{{ if not (semverLessThan $version "8.7.0") }} | ||
xpack.fleet.enableExperimental: ["experimentalDataStreamSettings"] # Enable experimental toggles in Fleet UI | ||
{{ end }} | ||
|
||
xpack.encryptedSavedObjects.encryptionKey: "12345678901234567890123456789012" | ||
|
||
{{ if not (semverLessThan $version "8.1.0") }} | ||
xpack.cloudSecurityPosture.enabled: true | ||
{{ end }} |
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.
Nice! Having these templates is going to be easier to add new features depending on the version, thanks!!
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.
👍
Testing with integrations in elastic/integrations#5252. |
/test |
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.
LGTM!
Conflicts will be high likely because of updating of the package-registry version used by default in Elastic stack to v1.19.0
.
💚 Build Succeeded
cc @jsoriano |
Introduce several refactors to decouple profiles from stack resources, with the target of allowing the implementation of multiple stack providers and to try to establish better foundations for isolated and persistent profiles.
Note to reviewers: Sorry for the big change, but once files are moved and templatized it is difficult to keep this small. Let me know if you want a walk-through over zoom.
Changes here:
elastic-package profile use
command to select profile to use.Related issues: