Pass environment variables as "env" #171
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allows migration scripts to access the "env" variable, which can be used to change behaviour dynamically.
|
(Missed updating the table of contents, sorry—fixed in 9d6a828) |
minamijoyo
approved these changes
Apr 10, 2024
|
Shipped it in v0.3.21 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A small patch to allow migration scripts to access environment variables via the "env" variable, which allows some more dynamic behaviour when migrating. With this in place, it should also be trivial to add other variables and functions that make things more Terraform-like.
As part of this I added a call to
t.Setenvin the test setup—I don't think this should cause any issues, but if there's a better way of going about it let me know.Resolves #91.