-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add support for auto_healing_policies to google_compute_instance_group_manager. #185
Add support for auto_healing_policies to google_compute_instance_group_manager. #185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make testacc TEST=./google TESTARGS='-run=TestAccInstanceGroupManager_autoHealingPolicies'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./google -v -run=TestAccInstanceGroupManager_autoHealingPolicies -timeout 120m
=== RUN TestAccInstanceGroupManager_autoHealingPolicies
--- PASS: TestAccInstanceGroupManager_autoHealingPolicies (221.86s)
PASS
ok github.com/terraform-providers/terraform-provider-google/google 221.999s
👍 aside from one nit (feel free to merge after that)
@@ -646,3 +713,52 @@ func resourceSplitter(resource string) string { | |||
|
|||
return splits[len(splits)-1] | |||
} | |||
|
|||
func testAccInstanceGroupManager_autoHealingPolicies(template, target, igm, hck string) string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you put this above the little helper doodad so all the test configs are next to each other?
After the change:
|
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Add support for
auto_healing_policies
togoogle_compute_instance_group_manager
.Walking through the below list of scenarios, I saw the expected results:
CREATE v1
REFRESH v1
DESTROY v1
IMPORT v1
UPGRADE v1 to Beta
CREATE Beta
REFRESH Beta
DESTROY Beta
IMPORT Beta
UPGRADE Beta to v1
The weird cases were, as we expected:
UPGRADE v1 to Beta
- We can't read at Beta during the pre-apply refresh, so we don't catch out of band changes to Beta fieldsIMPORT Beta
- All resources are currently imported atv1
UPGRADE Beta to v1
- The post-apply read will be performed at Beta and notv1
, so the state file will have Beta self links. The next refresh will correct this.