-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
docs: clarify environment variable and system service relationship for config #19352
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -89,6 +89,12 @@ Here are detailed descriptions of each configuration method: | |
```yml | ||
license_key: {{MY_LICENSE_KEY}} | ||
``` | ||
<Callout variant="important"> | ||
Often the infrastructure agent will be running as a system service in the host, managed globally (e.g. `systemd` for Linux, Windows Services, `launchd` for macOS, etc). | ||
To apply configuration changes with environment variables in this setup, these environment variables will need to be set and made visible to the isolated context where the infrastructure agent service is running. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: To apply configuration changes with environment variables in this setup, these environment variables need to be set and made visible to the isolated context where the infrastructure agent service is running. |
||
The way of doing this is platform-dependent, check the documentation for your platform to add environment variables to system services. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Which documentation are you referring to? if there is another document I would suggest you to please add the link here. |
||
</Callout> | ||
</Collapser> | ||
|
||
<Collapser | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -37,6 +37,16 @@ | |
|
||
For an example of how all these variables can be used, see our [sample configuration template in GitHub](https://github.com/newrelic/infrastructure-agent/blob/master/assets/examples/infrastructure/newrelic-infra-template.yml.example). | ||
|
||
## Environment variables | ||
|
||
Many of the configuration options listed also admit using environment variables to set values, which will take precendence over the YAML configuration. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: Please remove "Will" |
||
|
||
<Callout variant="important"> | ||
Often the infrastructure agent will be running as a system service in the host, managed globally (e.g. `systemd` for Linux, Windows Services, `launchd` for macOS, etc). To apply configuration changes with environment variables in this setup, | ||
Check failure on line 45 in src/content/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx GitHub Actions / vale-linter
Check warning on line 45 in src/content/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx GitHub Actions / vale-linter
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: Often the infrastructure agent runs as a system service in the host |
||
these environment variables will need to be set and made visible to the isolated context where the infrastructure agent service is running. The way of doing this is platform-dependent, | ||
Check warning on line 46 in src/content/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx GitHub Actions / vale-linter
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: Please remove will from the sentence |
||
check the documentation for your platform to add environment variables to system services. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: Please add the link to "documentation" if we are referring to another document |
||
</Callout> | ||
|
||
## Agent variables [#agent-variables] | ||
|
||
<CollapserGroup> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: Often the infrastructure agent runs as a system service in the host, managed globally (e.g.
systemd
for Linux, Windows Services,launchd
for macOS, etc).