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

Ensure MY_POD_NAME and MY_POD_NAMESPACE envVar defined first #437

Merged
merged 2 commits into from
Nov 2, 2020

Conversation

ChunyiLyu
Copy link
Contributor

@ChunyiLyu ChunyiLyu commented Oct 30, 2020

This closes #433

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed

Summary Of Changes

  • handle the rabbitmq container envVar list as a special case if it's overwritten by override
  • we need to ensure that MY_POD_NAME and MY_POD_NAMESPACE are defined first so other envVars values can reference them

Additional Context

Local Testing

Added additional test about templating at unit. Have run unit and integration tests

- handle the rabbitmq container envVar list as a special case if it's overwritten by override
- we need to ensure that MY_POD_NAME and MY_POD_NAMESPACE are defined first so other envVars values can reference them
@mkuratczyk
Copy link
Collaborator

I took the liberty of adding K8S_SERVICE_NAME to the list of special variables.

@ChunyiLyu ChunyiLyu merged commit d0298dc into main Nov 2, 2020
@ChunyiLyu ChunyiLyu deleted the stsContainerEnvOverride branch November 2, 2020 09:59
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.

When using override to set an env variable, you can't refer to MY_POD_NAME and other variables
3 participants