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 docs: Fix parameter type and default value in client reserved configuration. into release/1.8.x #23418

Conversation

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

Backport

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

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


The reserved cores parameter in Nomad client agent configuration is int type, and default value is 0.

But according to the source codes, it is string type, and defalut value is empty string.

This part of the document has bothered me for a long time, so I want to fix it.


Overview of commits

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/liukch-client-agent-configuration/mentally-neat-sheepdog branch from aa19b8d to 3d836dc Compare June 21, 2024 20:30
@tgross tgross merged commit dded3cb into release/1.8.x Jun 21, 2024
5 of 7 checks passed
@tgross tgross deleted the backport/liukch-client-agent-configuration/mentally-neat-sheepdog branch June 21, 2024 20:31
Copy link

github-actions bot commented Jan 2, 2025

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants