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

Error handling for 404 responses from Azure on App Services #3198

Merged
merged 4 commits into from
Apr 6, 2019
Merged

Error handling for 404 responses from Azure on App Services #3198

merged 4 commits into from
Apr 6, 2019

Conversation

IanMoroney
Copy link
Contributor

Similar to how the issue was solved for Azure Functions See here the requisite error handling is missing for App Services when 404's are thrown by Azure.

Should resolve issues like:
Error refreshing state.
azurerm_app_service_slot.aps: Error making Read request on AzureRM AppService SlotConfiguration "xxxxx": web.AppsClient#GetConfigurationSlot: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Web/sites/xxxxx" under resource group 'xxxxxxxx' was not found."

and the same for app service, for both app settings and configuration.

Enhancing error handling for app service slot app settings
Enhancing error handling for app service app settings
Enhancing error handling for app service configuration
Enhancing error handling for app service configuration
Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

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

LGTM - thanks for this @IanMoroney

@tombuildsstuff tombuildsstuff merged commit e3c9929 into hashicorp:master Apr 6, 2019
tombuildsstuff added a commit that referenced this pull request Apr 6, 2019
@ghost
Copy link

ghost commented Apr 17, 2019

This has been released in version 1.25.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.25.0"
}
# ... other configuration ...

@IanMoroney IanMoroney deleted the patch-1 branch April 17, 2019 13:00
@ghost
Copy link

ghost commented May 6, 2019

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 May 6, 2019
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