Skip to content

Coerce env var values to empty string#23

Open
cywang117 wants to merge 1 commit intomainfrom
coerce-null-env-vars
Open

Coerce env var values to empty string#23
cywang117 wants to merge 1 commit intomainfrom
coerce-null-env-vars

Conversation

@cywang117
Copy link
Copy Markdown
Contributor

Upstream API doesn't accept null/undefined for
env var values, so we coerce to empty string just
as balena-compose <=v7 (prior to compose-parser integration) did.

Change-type: patch

@flowzone-app flowzone-app Bot enabled auto-merge May 6, 2026 19:02
@cywang117
Copy link
Copy Markdown
Contributor Author

/rebase

Upstream API doesn't accept null/undefined for
env var values, so we coerce to empty string just
as balena-compose <=v7 (prior to compose-parser integration) did.

Change-type: patch
@git-basejump git-basejump Bot force-pushed the coerce-null-env-vars branch from fcbaf4e to a68e83c Compare May 6, 2026 19:56
environment:
EXPLICIT_VALUE: hello
EXPLICIT_EMPTY: ""
NULL_DICT_FORM: null
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

we should add an UNDEFINED_FORM: which is also accepted by compose. Weirdly docker-compose removes explicit fields defined with null but I saw that is not the same behavior of compose-go

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