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

Backport of client: remove null dynamic metadata keys into release/1.6.x #18674

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #18664 to be assessed for backporting due to the inclusion of the label backport/1.6.x.

The below text is copied from the body of the original PR.


Setting a null value to a node metadata is expected to remove it from subsequent reads. This is true both for static node metadata (defined in the agent configuration file) as well as for dynamic node metadata (defined via the Nomad API).

Null values for static metadata must be persisted to indicate that the value has been removed, but strictly dynamic metadata null values can be removed from state and client memory.

Closes #18603


Overview of commits

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-cleanup-dynamic-node-metadata/sadly-legible-albacore branch 2 times, most recently from 193ebce to c68c8c9 Compare October 5, 2023 15:44
@vercel vercel bot temporarily deployed to Preview – nomad October 5, 2023 15:47 Inactive
@vercel vercel bot temporarily deployed to Preview – nomad-storybook-and-ui October 5, 2023 15:53 Inactive
@lgfa29 lgfa29 merged commit 79c3d25 into release/1.6.x Oct 5, 2023
21 checks passed
@lgfa29 lgfa29 deleted the backport/b-cleanup-dynamic-node-metadata/sadly-legible-albacore branch October 5, 2023 16:14
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.

2 participants