Skip to content

[elastic/shared] Remove system managed template fields#829

Merged
inqueue merged 1 commit intoelastic:masterfrom
inqueue:20250729-elogs-templates-bug
Jul 29, 2025
Merged

[elastic/shared] Remove system managed template fields#829
inqueue merged 1 commit intoelastic:masterfrom
inqueue:20250729-elogs-templates-bug

Conversation

@inqueue
Copy link
Member

@inqueue inqueue commented Jul 29, 2025

Remove system fields when updating templates.

Closes #828

@inqueue inqueue requested a review from a team July 29, 2025 22:10
Comment on lines +29 to +30
original.pop("created_date_millis", None)
original.pop("modified_date_millis", None)
Copy link

Choose a reason for hiding this comment

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

just for transparency, doubt a problem, but we can also return {created,modified}_date which is human-readable, which is only returned if we supply the ?human=true HTTP param

but doubt that's an issue here...

Copy link
Member Author

Choose a reason for hiding this comment

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

It isn't an issue here, but that would be a nice to have for the API.

@inqueue inqueue merged commit 48f2566 into elastic:master Jul 29, 2025
13 checks passed
@inqueue inqueue deleted the 20250729-elogs-templates-bug branch August 4, 2025 14:30
inqueue added a commit to inqueue/rally-tracks that referenced this pull request Aug 19, 2025
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@inqueue
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

elastic/shared component template update is broken

3 participants