provider/google: Fix project metadata sshkeys from showing up #4512
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addressing #4504
The fix I made is to ignore any project metadata pairs that do not show up in the users config.
sshKeys
,gke-cluster-<id>-cidr
, andstackdriver-key
are a few examples of keys that are generated by GCP depending on a users existing infrastructure that would be overwritten by Terraform if not ignored duringRead
.@phinze