add "global" harness configs plumbed through provider configs #7
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
|
similar logic to #4, since we're still in early pre-release phase and not used anywhere, I'm going to merge without a formal review. |
joshrwolf
force-pushed
the
provider-configs
branch
9 times, most recently
from
e5da9ff
to
12eb1ba
Compare
joshrwolf
force-pushed
the
provider-configs
branch
from
12eb1ba
to
c0b4cfa
Compare
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.
this PR:
harnessespackage to split up each harness into its own package. this supports the namespacing needed to support the additional configs + variadic optionsproviderconfigsTF_ACC=1tests