-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TF Acceptance Tests #165
Labels
enhancement
New feature or request
Comments
benesch
added a commit
that referenced
this issue
Jun 5, 2023
Gracefully handle the situation where a resource has gone missing outside of Terraform (e.g., because the user manually ran a `DROP` command). This logic was applied to table resources as a one-off in #155, but that code appears to have gotten lost in 9235b4b. This commit re-adds the logic for all resource types. No tests, because our current testing infrastructure is not powerful enough to handle this. Will put up a test in a separate PR that enhances the testing infrastructure (see #165). Fix #157.
benesch
added a commit
that referenced
this issue
Jun 5, 2023
Terraform has a standard acceptance testing framework [0] that allows for testing the complete lifecyle of provider resources: apply, plan, refresh, destroy, etc. In particular, this makes it possible to test things like a resource going missing due to a manual drop (#157). This commit wires up the acceptance test framework, and then adds some basic acceptance tests for creating secrets, creating cluster replicas, and refreshing state for disappearing secrets. Ultimately I think we should move all of today's integration tests to this acceptance test framework. Work towards #165. [0]: https://developer.hashicorp.com/terraform/plugin/testing/acceptance-tests
benesch
added a commit
that referenced
this issue
Jun 5, 2023
Terraform has a standard acceptance testing framework [0] that allows for testing the complete lifecyle of provider resources: apply, plan, refresh, destroy, etc. In particular, this makes it possible to test things like a resource going missing due to a manual drop (#157). This commit wires up the acceptance test framework, and then adds some basic acceptance tests for creating secrets, creating cluster replicas, and refreshing state for disappearing secrets. Ultimately I think we should move all of today's integration tests to this acceptance test framework. Work towards #165. [0]: https://developer.hashicorp.com/terraform/plugin/testing/acceptance-tests
Merged
Remaining resources that will need acceptance tests after #177 is merged.
|
dehume
pushed a commit
that referenced
this issue
Jun 12, 2023
* Add acceptance tests Terraform has a standard acceptance testing framework [0] that allows for testing the complete lifecyle of provider resources: apply, plan, refresh, destroy, etc. In particular, this makes it possible to test things like a resource going missing due to a manual drop (#157). This commit wires up the acceptance test framework, and then adds some basic acceptance tests for creating secrets, creating cluster replicas, and refreshing state for disappearing secrets. Ultimately I think we should move all of today's integration tests to this acceptance test framework. Work towards #165.
Will be covered in two PRs: |
This was
linked to
pull requests
Jun 13, 2023
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the integration tests with the docker compose using the Materialize image only does
apply
->plan
->destroy
. It would be good to also tests applicable updates and have a flow of:apply
->plan
->update
->plan
->destroy
.The text was updated successfully, but these errors were encountered: