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
HPCC-25946 Add environment variables helm chart setting to doc #16539
HPCC-25946 Add environment variables helm chart setting to doc #16539
Conversation
Signed-off-by: g-pan <greg.panagiotatos@lexisnexis.com>
https://track.hpccsystems.com/browse/HPCC-25946 |
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.
Question / comment inline
environment values are defined under the <emphasis>#env:</emphasis> | ||
portion of the delivered values.yaml as illustrated below.</para> | ||
|
||
<programlisting>#env: |
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.
Shouldn't these be uncommented in the example?
<title>Environment Values</title> | ||
|
||
<para>You can define Environment Variables in a YAML file. The | ||
environment values are defined under the <emphasis>#env:</emphasis> |
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.
env: rather than #env: (similar to jim's comment below)
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.
Actually it should be global.env
environment values are defined under the <emphasis>#env:</emphasis> | ||
portion of the delivered values.yaml as illustrated below.</para> | ||
|
||
<programlisting>#env: |
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.
should be
global:
env:
- name: SMTPserver
- value: mysmtpserver
You can also specify environment variables for each individual component. Has that been documented?
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.
no. this is the first mention of env
will see to add it here
Signed-off-by: g-pan <greg.panagiotatos@lexisnexis.com>
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.
Good from my POV.
<programlisting>global: | ||
env: | ||
- name: SMTPserver | ||
- value: mysmtpserver</programlisting> |
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.
There shouldn't be a leading '-' before value, otherwise it will create a new list entry, and fail the schema validation.
|
||
<para>You can define Environment Variables in a YAML file. The | ||
environment values are defined under the | ||
<emphasis>global.env:</emphasis> portion of the delivered values.yaml |
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.
probably better without the trailing :
<para>You can define Environment Variables in a YAML file. The | ||
environment values are defined under the | ||
<emphasis>global.env:</emphasis> portion of the delivered values.yaml | ||
as illustrated below.</para> |
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.
as a list of name value pairs, as illustrated below.
Otherwise you haven't really described the format.
- name: SMTPserver | ||
- value: mysmtpserver</programlisting> | ||
|
||
<para>The global.env section of the delivered values file adds default |
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.
question: What does the phrase "delivered values file" mean?
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.
referring to the default/stock https://github.com/hpcc-systems/HPCC-Platform/blob/master/helm/hpcc/values.yaml file,
is there a better way to refer to it?
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.
perhaps "the supplied values.yaml file" is better?
Signed-off-by: g-pan <greg.panagiotatos@lexisnexis.com>
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.
Good from my POV
See page 47 compiled book, PDF available upon request.
Signed-off-by: g-pan greg.panagiotatos@lexisnexis.com
Type of change:
Checklist:
Smoketest:
Testing:
Successful integration testing: http://10.224.20.18/view/Docs-gp/job/Doc-Build-04-GPRepo2