Issue sweeping - Terraform 0.12.2, Windows, Docker & PLY #65
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.
Before I dump all this on you:
into a bunch of things before I got everything working again.
Changeset
/data
for consistency with the majority of containersThis is also exposed as a
VOLUME ["/data"]
for overwriting withcustom images. Not all use cases will need the overlayfs
blast-radius:latest
a second tag is pushed to the registry:docker push blast-radius:$TF_VERSION
- Version locking is extremelyessential with TF Cloud given remove state files can't always be rewound
return it to a functional state
seemingly at random) in favor of asserting the existance of a prefix.
get
andinit
through overridable usageof
TF_CLI_ARGS_*
-- This is also used for Terraform 0.12 credentialsand workspaces (an example is in the
docker-compose.yml
)requirements.txt
, allowing Docker tobenefit from layer caching when no packages are changed.
setup.py
as well as removal of legacy keys. I didn'treplace them all, but I got sleepy and wanted to open this up.
Should affect positive change for #24 #28 #33 #36 #43 #54 -- Not
necessarily 100% fixes but at least normalizes the Docker runtime.
Anyways... 🎉