module.vault-deploy.data.local_file.vault-version: Reading...
module.vault-deploy.data.local_file.vault-version: Read complete after 0s [id=b2c42c62b223300eef494f3ef461f18df48f6a90]
module.vault-deploy.data.google_project.current: Reading...
module.vault-deploy.google_kms_key_ring.vault-production: Refreshing state... [id=projects/jtcressy-net-235001/locations/global/keyRings/vault-production]
module.vault-deploy.data.google_iam_policy.noauth: Reading...
module.vault-deploy.google_service_account.vault: Refreshing state... [id=projects/jtcressy-net-235001/serviceAccounts/vault-sa@jtcressy-net-235001.iam.gserviceaccount.com]
module.vault-deploy.google_storage_bucket.vault: Refreshing state... [id=vault-jtcressy-net]
module.vault-deploy.data.google_iam_policy.noauth: Read complete after 0s [id=3450855414]
module.vault-deploy.google_storage_bucket_iam_member.vault: Refreshing state... [id=b/vault-jtcressy-net/roles/storage.objectAdmin/serviceAccount:vault-sa@jtcressy-net-235001.iam.gserviceaccount.com]
module.vault-deploy.google_kms_key_ring_iam_member.vault: Refreshing state... [id=projects/jtcressy-net-235001/locations/global/keyRings/vault-production/roles/owner/serviceAccount:vault-sa@jtcressy-net-235001.iam.gserviceaccount.com]
module.vault-deploy.google_kms_crypto_key.vault: Refreshing state... [id=global/vault-production/vault-key]
module.vault-deploy.data.google_project.current: Read complete after 1s [id=projects/jtcressy-net-235001]
module.vault-deploy.google_cloud_run_service.vault: Refreshing state... [id=locations/us-central1/namespaces/jtcressy-net-235001/services/vault]
module.vault-deploy.google_cloud_run_service_iam_policy.noauth: Refreshing state... [id=v1/projects/jtcressy-net-235001/locations/us-central1/services/vault]
module.vault-deploy.google_cloud_run_domain_mapping.vault: Refreshing state... [id=locations/us-central1/namespaces/jtcressy-net-235001/domainmappings/vault.jtcressy.net]
Note: Objects have changed outside of Terraform
Terraform detected the following changes made outside of Terraform since the
last "terraform apply" which may have affected this plan:
# module.vault-deploy.google_cloud_run_service.vault has changed
~ resource "google_cloud_run_service" "vault" {
id = "locations/us-central1/namespaces/jtcressy-net-235001/services/vault"
name = "vault"
# (4 unchanged attributes hidden)
~ metadata {
~ annotations = {
+ "run.googleapis.com/urls" = jsonencode(
[
+ "https://vault-313081364289.us-central1.run.app",
+ "https://vault-t4wee7sm2q-uc.a.run.app",
]
)
# (5 unchanged elements hidden)
}
# (6 unchanged attributes hidden)
}
# (2 unchanged blocks hidden)
}
# module.vault-deploy.google_kms_crypto_key.vault has changed
~ resource "google_kms_crypto_key" "vault" {
~ destroy_scheduled_duration = "86400s" -> "2592000s"
id = "global/vault-production/vault-key"
name = "vault-key"
# (6 unchanged attributes hidden)
# (2 unchanged blocks hidden)
}
# module.vault-deploy.google_storage_bucket.vault has changed
~ resource "google_storage_bucket" "vault" {
id = "vault-jtcressy-net"
name = "vault-jtcressy-net"
# (11 unchanged attributes hidden)
+ soft_delete_policy {
+ effective_time = "2024-03-01T08:00:00.000Z"
+ retention_duration_seconds = 604800
}
# (1 unchanged block hidden)
}
This is a refresh-only plan, so Terraform will not take any actions to undo
these. If you were expecting these changes then you can apply this plan to
record the updated values in the Terraform state without changing any remote
objects.
─────────────────────────────────────────────────────────────────────────────
Saved the plan to: tfplan
To perform exactly these actions, run the following command to apply:
terraform apply "tfplan"
Configuration drift was detected on the last Terraform run. Inspect the job logs to see what's changed and kick off a manual apply to correct the drift.
Show Plan