PSS: Add tests showing provider commands being used with PSS
#37959
+243
−1
Conversation
This file contains hidden or 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
SarahFrench
added
the
no-changelog-needed
SarahFrench
force-pushed
the
pss/pss-with-state-commands
branch
3 times, most recently
from
bb7d519 to
c2d9c42
Compare
…ers` command Note: I've excluded the `terraform providers locks` and `terraform providers mirror` commands as they don't interact with backends.
… `providers` command
… `providers schema` command
SarahFrench
force-pushed
the
pss/pss-with-provider-commands
branch
from
1ab5e53 to
f9d9db3
Compare
Member
Author
|
TODO: Tests should make assertions about the schema of the store itself being in the returned schema. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Following #37569, this PR demonstrates that the
providercommands -that interact with backends- work when pluggable state storage is in use.The E2E tests rely on a test fixture resembling a fully initialised working directory, including some local state describing an instance of the terraform_data resource. That state is inspected by the commands in the tests.
The integration tests use an existing test fixture because some state_store config needs to be present for the test, but the state present in tests is contained within the mock provider definition.
Target Release
1.15.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry