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

d/App Service Plan: handling a 404 not being returned as an error #849

Merged
merged 1 commit into from
Feb 16, 2018

Conversation

tombuildsstuff
Copy link
Contributor

Fixes #766

Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

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

LGTM

return fmt.Errorf("Error making Read request on App Service Plan %q (Resource Group %q): %+v", name, resourceGroup, err)
}

if utils.ResponseWasNotFound(resp.Response) {
Copy link
Member

Choose a reason for hiding this comment

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

Does this change need to be rolled out to all of the resources? Or is this just app service plan specific?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it appears to be resource dependent, unfortunately - so we'll need to go through the lot (although, that's outside the scope of this PR)

@tombuildsstuff tombuildsstuff merged commit 98a4834 into master Feb 16, 2018
tombuildsstuff added a commit that referenced this pull request Feb 16, 2018
@tombuildsstuff tombuildsstuff deleted the app-service-plan-data-source-crash branch March 5, 2018 20:48
@ghost
Copy link

ghost commented Mar 31, 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!

@ghost ghost locked and limited conversation to collaborators Mar 31, 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.

Crash while handling Not Found response
2 participants