You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.
When you run terraform apply after creating the resource, we are trying to update the private_key when it is sensitive and will always be different. We should avoid updating the
resource:
When you run terraform apply after creating a gcp resource, we were
trying to update the `private_key` when it is a sensitive element and
the Lacework server, for security reasons, doesn't return that secret,
which means that the resource was always different.
We are adding a suppression to avoid updating the resource.
Closes#4
Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
When you run terraform apply after creating a gcp resource, we were
trying to update the `private_key` when it is a sensitive element and
the Lacework server, for security reasons, doesn't return that secret,
which means that the resource was always different.
We are adding a suppression to avoid updating the resource.
Closes#4
Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
When you run terraform apply after creating a gcp resource, we were
trying to update the `private_key` when it is a sensitive element and
the Lacework server, for security reasons, doesn't return that secret,
which means that the resource was always different.
We are adding a suppression to avoid updating the resource.
Closeshashicorp/terraform-provider-lacework#4
Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When you run
terraform apply
after creating the resource, we are trying to update theprivate_key
when it is sensitive and will always be different. We should avoid updating theresource:
The text was updated successfully, but these errors were encountered: