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

expose env variables #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

expose env variables #2

wants to merge 1 commit into from

Conversation

woodpig07
Copy link
Contributor

for #1

healthcheck({
path: '/test',
versionFile: './package.json'
versionFile: './package.json',
env: {
Copy link
Member

Choose a reason for hiding this comment

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

why not just pass a list instead,

Suggested change
env: {
env: ['TEST_VAR_1', 'TEST_VAR_2]

Choose a reason for hiding this comment

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

It seems it's using a object to let you define the alias of the VAR name used for component. e.g

env: { 'alias1': 'VAR_NAME_1' }

while in deployment the env var is named as VAR_NAME_1.

@zbal
Copy link
Member

zbal commented Sep 23, 2020

Can we get a follow up on this ? I'd love to see that mainstream in our components.... @xavierchow @CCharlieLi care to review / merge / proceed with this ?

@xavierchow
Copy link
Member

don't merge this, we still have unaligned opened discussion: #1.

@zbal zbal mentioned this pull request Sep 25, 2020
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.

4 participants