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

env: resolve env vars in order #1519

Merged
merged 3 commits into from
Jan 26, 2024
Merged

env: resolve env vars in order #1519

merged 3 commits into from
Jan 26, 2024

Conversation

jdx
Copy link
Owner

@jdx jdx commented Jan 24, 2024

This is a major refactor of how env vars are handled. Previously, they were resolved as part of parsing but they really need to be done one at a time so that the results of each var can be used for the next one. This should also make it possible to greatly simplify how env vars are handled in tools by using the same logic.

Fixes #1262
Prereq for #1447
Prereq for #1303
Prereq for #1261

@jdx jdx force-pushed the env-man branch 3 times, most recently from 7fc3b23 to 871abf9 Compare January 25, 2024 00:48
@jdx jdx changed the title env-man env: resolve env vars in order Jan 25, 2024
@jdx
Copy link
Owner Author

jdx commented Jan 25, 2024

@Ajpantuso wanted to draw your attention to this PR just so you're aware of it since I know you worked on some of the env stuff a bit. I'd hold off on any env-related things for a couple of days until I can get this out since all of that logic is going to change.

@jdx jdx force-pushed the env-man branch 12 times, most recently from 3165305 to 44cab31 Compare January 26, 2024 20:01
@jdx jdx marked this pull request as ready for review January 26, 2024 22:46
@jdx jdx enabled auto-merge (squash) January 26, 2024 22:50
@jdx jdx merged commit 7dce359 into main Jan 26, 2024
9 checks passed
@jdx jdx deleted the env-man branch January 26, 2024 22:52
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 env variables to reference previously defined env vars in same configuration file
2 participants