-
Notifications
You must be signed in to change notification settings - Fork 325
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
drift detected immediately after apply #1096
Comments
@zam6ak I tried to reproduce this using just a realm as a simple example and everything worked as expected. Can you try to provide a minimal example I can use to reproduce this? |
@sschu I can certainly try # change provider settings in root "main.tf" to match your environment,
# then init and verify install providers
terraform init
terraform providers
# preview and then apply changes
terraform plan
terraform apply
# recheck plan - shows no changes
terraform plan
# but drift exists when using -refresh-only
terraform plan -refresh-only notice the "Object have changed outside of Terraform" output...
|
Describe the bug
Hi
We have a TF project using Keycloak provider v5.1.0 that creates several realms, multiple clients in each, users, etc, etc.
So far this is working but we have noticed that specific resources, after they are created, are "drifting"
So if we run
terraform apply
and then immediately follow up withterraform apply -refresh-only
, I get a lot of resources noted asI am noticing a pattern where some attributes of certain resources are causing this drift
Below is a paired down output of
terraform apply -refresh-only
shows examples of attributes inkeycloak_realm
,keycloak_openid_client
andkeycloak_user
but there are others as wellVersion
26.1.0
Expected behavior
no drift should exist immediately after
terraform apply
Actual behavior
No response
How to Reproduce?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: