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

Disable subobjects by default on new packages and data streams #1965

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

jsoriano
Copy link
Member

Modify the archetypes used by elastic-package create to disable subobjects by default on new packages and data streams.

A new question is added to the survey so users can chose to opt out for this behavior.

Closes #1872.

@jsoriano jsoriano requested review from flash1293 and a team July 10, 2024 20:10
@jsoriano jsoriano self-assigned this Jul 10, 2024
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jul 10, 2024

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @jsoriano

Comment on lines +77 to +82
{{ if .Manifest.Elasticsearch.SourceMode }}
source_mode: {{ .Manifest.Elasticsearch.SourceMode }}
{{- end}}
{{ if .Manifest.Elasticsearch.IndexMode }}
index_mode: {{ .Manifest.Elasticsearch.IndexMode }}
{{- end }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, there are no questions for these values when creating the package. So, right now they would not be written here in this manifest.

Should they be added also as part of the questions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure, I could add them in a follow up if necessary. Or would you prefer the questions to be added here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, they can be added in a follow up, it's not needed to do it now.

Copy link
Contributor

@mrodm mrodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Comment on lines +77 to +82
{{ if .Manifest.Elasticsearch.SourceMode }}
source_mode: {{ .Manifest.Elasticsearch.SourceMode }}
{{- end}}
{{ if .Manifest.Elasticsearch.IndexMode }}
index_mode: {{ .Manifest.Elasticsearch.IndexMode }}
{{- end }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, they can be added in a follow up, it's not needed to do it now.

@jsoriano jsoriano merged commit 63816a7 into elastic:main Jul 11, 2024
3 checks passed
@jsoriano jsoriano deleted the archetype-subobjects-false branch July 11, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fleet: Make subobjects: false the default for all data streams
3 participants