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

azurerm_traffic_manager_profile - add expected_status_code_ranges #5471

Merged
merged 2 commits into from Jan 22, 2020

Conversation

katbyte
Copy link
Collaborator

@katbyte katbyte commented Jan 22, 2020

also changes some TypeSets -> TypeLists as the API ignores all but the first element

Copy link
Member

@jackofallops jackofallops left a comment

Choose a reason for hiding this comment

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

One minor comment, otherwise LGTM.

@@ -194,7 +212,7 @@ func resourceArmTrafficManagerProfileCreateUpdate(d *schema.ResourceData, meta i

read, err := client.Get(ctx, resGroup, name)
if err != nil {
return err
return fmt.Errorf("Error reading TrafficManager profile %s (resource group %s): %v", name, resGroup, err)
Copy link
Member

Choose a reason for hiding this comment

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

Should we update this to resourceGroup as elsewhere in the provider?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Not a bad idea! done

@katbyte katbyte merged commit 10638a1 into master Jan 22, 2020
@katbyte katbyte deleted the kt/traffic-status-codes branch January 22, 2020 18:12
katbyte added a commit that referenced this pull request Jan 22, 2020
@ghost
Copy link

ghost commented Jan 27, 2020

This has been released in version 1.42.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.42.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 28, 2020

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Mar 28, 2020
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.

None yet

2 participants