chore: update agent config with cluster name #148
Merged
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.
What does this PR do
This pull request includes several changes to support the addition of a new
cluster_name
label in the configuration and API code. The most important changes include updates to thetask_config_tpl.dat
file and modifications to thegetAgentIngestConfigs
function inremote_config.go
.Configuration Updates:
config/setup/common/data/task_config_tpl.dat
: Addedcluster_name
label to the configuration template to ensure the cluster name is included in the task configuration. [1] [2]API Code Updates:
modules/agent/api/remote_config.go
: AddedclusterName
variable and included it in the configuration string to pass the cluster name through the API. [1] [2] [3]Rationale for this change
Standards checklist