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
Terraform validator supports an "offline" mode which purposely does not configure the provider for GCP access. However, the expandBootDisk function for compute_instance assumes that the provider is configured for GCP access. We should silently skip this verification (at least when offline), because terraform validator is not responsible for validating that the configuration is correct, just that it complies with policies.
This is somewhat complicated by the fact that expandBootDisk is currently manually "shared" between terraform-provider-google and terraform-google-conversion (i.e. copy-pasted from one to the other.)
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform validator supports an "offline" mode which purposely does not configure the provider for GCP access. However, the expandBootDisk function for compute_instance assumes that the provider is configured for GCP access. We should silently skip this verification (at least when offline), because terraform validator is not responsible for validating that the configuration is correct, just that it complies with policies.
This is somewhat complicated by the fact that expandBootDisk is currently manually "shared" between terraform-provider-google and terraform-google-conversion (i.e. copy-pasted from one to the other.)
The text was updated successfully, but these errors were encountered: