-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
So we've got
[1m[31mError: [0m[0m[1mProvider produced inconsistent result after apply[0m
[0mWhen applying changes to
vaulted_vault_secret.checkouts_tf_checkouts_database_sumup_name, provider
"registry.terraform.io/-/vaulted" produced an unexpected new value for was
present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
the terraform code change that lead to the error is shown below.
Two resources are removed and other two added but with the same path.(not entirely smart idea but still)
diff --git a/vault/theta/checkouts.tf b/vault/theta/checkouts.tf
index ff194b7..5975d00 100644
--- a/vault/theta/checkouts.tf
+++ b/vault/theta/checkouts.tf
@@ -1,15 +1,3 @@
-resource "vaulted_vault_secret" "vault_encrypted_secret_checkouts_database_sumup_name" {
- path = "secret/checkouts/database/sumup/name"
-
- payload_json = "$VED;1.0::U+2aJHNP ... oqdt9"
-}
-
-resource "vaulted_vault_secret" "vault_encrypted_secret_checkouts_database_sumup_schema" {
- path = "secret/checkouts/database/sumup/schema"
-
- payload_json = "$VED;1.0::qlI3....NTlw=="
-}
-
...
+
+resource "vaulted_vault_secret" "checkouts_tf_checkouts_database_sumup_schema" {
+ "path" = "secret/checkouts/database/sumup/schema"
+
+ "payload_json" = "$VED;1.0::c3... WV3OA="
+}
+
+resource "vaulted_vault_secret" "checkouts_tf_checkouts_database_sumup_name" {
+ "path" = "secret/checkouts/database/sumup/name"
+
+ "payload_json" = "$VED;1.0::ArO... SkaJudh6BfjiU="
+}
You might find this issue report useful.
Thanks
Rado.
Metadata
Metadata
Assignees
Labels
No labels