feat: cached multi-runner #8
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
strophy
force-pushed
the
feat/cached-multi-runner
branch
from
8e4b1a2
to
69f3d1f
Compare
strophy
force-pushed
the
feat/cached-multi-runner
branch
from
709800e
to
f8dff3b
Compare
5 tasks
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.
Our config was becoming extremely complicated and disorganized. This PR is an effort to follow Terraform best practices and reproduce the structure of the upstream project to implement our caching as a module, move to a multi-runner config, and augment that config to control cache setup. This should allow us to destroy the two separate TF workspaces for core and platform, simplifying our deployment.