This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Making machine identity a parameter of the agent config #2649
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
This is part of the unmanaged node work
This PR introduces
MachineIdentity
as new configuration field to the agent and the tasks.It contains the
machine_name
,machine_id
andscaleset name
.When setting this field on the agent, we bypass the current behavior of reading those values from files or the environment.
This allows multiple instances of the agent on the same machine to behave as different nodes.
The existing behavior stays the same when the
MachineIdentity
is not specified in the configcloses #2521