Skip to content
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

Handle null iap block in BackendService #1668

Conversation

rileykarson
Copy link
Member

Fixes hashicorp/terraform-provider-google#3441

This isn't feasible to test in an acc test, but I verified this worked locally by creating a service with the API explorer that didn't have the block present.

Annoyingly, the block is a case where it defaults to disabled so we ran into this error when a user had used an old resource; users could also encounter it when importing though. We've sent a default block since version 1.2 of the provider, so on any resources created since this was a non-issue.


[all]

[terraform]

[terraform-beta]

[ansible]

[inspec]

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician, I work on Magic Modules.
This PR seems not to have generated downstream PRs before, as of 20fe3f7.

Pull request statuses

No diff detected in terraform-google-conversion.
No diff detected in Ansible.
No diff detected in Inspec.

New Pull Requests

I built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: hashicorp/terraform-provider-google-beta#623
depends: hashicorp/terraform-provider-google#3460

@rileykarson
Copy link
Member Author

Oops accidentally duplicates #1667

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

Successfully merging this pull request may close these issues.

BackendService crash from blank IAP value in 2.4.0
3 participants