Skip to content
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.

fix(gcp): suppress private key diff to avoid updates #10

Merged
merged 1 commit into from
Jul 23, 2020

Conversation

afiune
Copy link
Contributor

@afiune afiune commented Jul 23, 2020

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>
@afiune afiune added the bug label Jul 23, 2020
@afiune afiune requested a review from scottford-lw July 23, 2020 16:30
@afiune afiune self-assigned this Jul 23, 2020
@ghost ghost added the size/XS label Jul 23, 2020
Copy link
Contributor

@scottford-lw scottford-lw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Great stuff!!!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix(gcp): Avoid updating resource on second terraform apply
2 participants