Skip to content

Allow config env vars to be empty#1794

Merged
carolynvs merged 1 commit intogetporter:release/v1from
carolynvs:fix-empty-config-vars
Oct 13, 2021
Merged

Allow config env vars to be empty#1794
carolynvs merged 1 commit intogetporter:release/v1from
carolynvs:fix-empty-config-vars

Conversation

@carolynvs
Copy link
Member

What does this change

Consider an empty environment variable as set, so that you can do things like PORTER_DEFAULT_STORAGE= and have
that override what is in the config file.

I am using this in the Porter Operator to be able to switch which storage backend I am using with an environment variable, and not have to edit the file.

What issue does it fix

N/A

Notes for the reviewer

N/A

Checklist

  • Unit Tests
  • Documentation
  • Schema (porter.yaml)

Consider an empty environment variable as set,
so that you can do things like PORTER_DEFAULT_STORAGE= and have
that override what is in the config file

Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
@carolynvs carolynvs force-pushed the fix-empty-config-vars branch from 6b2ace9 to e3f787a Compare October 13, 2021 16:01
@carolynvs carolynvs merged commit e5e397a into getporter:release/v1 Oct 13, 2021
@carolynvs carolynvs deleted the fix-empty-config-vars branch October 13, 2021 17:00
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.

2 participants