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

Provide helper Pod params as env vars. #177

Merged

Conversation

mgoltzsche
Copy link
Contributor

@mgoltzsche mgoltzsche commented Mar 6, 2021

For backward compatibility the CLI options are still provided.

Closes #175
Split from PR #166

@mgoltzsche mgoltzsche force-pushed the provide_params_as_env_vars_to_helper_pod branch from 1e35811 to 45b75fe Compare March 6, 2021 20:46
@mgoltzsche mgoltzsche force-pushed the provide_params_as_env_vars_to_helper_pod branch 2 times, most recently from 8731622 to 6758ec6 Compare March 6, 2021 20:55
@mgoltzsche mgoltzsche force-pushed the provide_params_as_env_vars_to_helper_pod branch 2 times, most recently from 12dbd1f to 5a0f570 Compare March 17, 2022 01:11
For backward compatibility the CLI options are still provided.

Closes rancher#175

Signed-off-by: Max Goltzsche <max.goltzsche@gmail.com>
@mgoltzsche mgoltzsche force-pushed the provide_params_as_env_vars_to_helper_pod branch from 5a0f570 to f073e86 Compare March 17, 2022 01:15
@mgoltzsche
Copy link
Contributor Author

@derekbit this PR is also ready for review - I just rebased it.

@derekbit
Copy link
Member

@mgoltzsche
Could you elaborate more the purpose of moving the the variables (absolutePath, sizeInBytes and volMode) to env variables? This will be helpful for understanding the series of the PRs clearly.

@mgoltzsche
Copy link
Contributor Author

mgoltzsche commented Mar 20, 2022

This PR reduces the amount of redundant boilerplate code needed to configure a helper pod (the option-to-env-var mapping is the same for all setup and the teardown scripts), following the twelve-factor app practices.

Before I provide a PR for #164 I wanted to clean that up and avoid breaking helper pod configurations that eventually exist already and would fail if a new parameter would be provided that is unknown to them.

Copy link
Member

@derekbit derekbit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow the helper pod to read params from env vars
2 participants