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

app configuration breaking change: the api now returns the resource group name in the ID in lowercase now #6606

Closed
katbyte opened this issue Jan 6, 2020 · 4 comments
Assignees
Labels
App Services bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team.
Milestone

Comments

@katbyte
Copy link

katbyte commented Jan 6, 2020

Bug Report

  • import path of package in question, e.g. .../services/compute/mgmt/2018-06-01/compute
    "github.com/Azure/azure-sdk-for-go/services/appconfiguration/mgmt/2019-10-01/appconfiguration"
  • SDK version e.g. master, latest, 18.1.0
[13:07:52] kt@katbook:~/hashi/tf/azure/azurerm▸master$ cat go.mod | egrep "(autorest|Azure)"
	github.com/Azure/azure-sdk-for-go v36.2.0+incompatible
	github.com/Azure/go-autorest/autorest v0.9.3
	github.com/Azure/go-autorest/autorest/date v0.2.0
  • output of go version
go version go1.13.1 darwin/amd64
  • What happened?
    Sometime in the last couple days the appconfiguration api behaviour changed how it handles resource group names. The resource group name now appears to be returned in lowercase:

put https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestRG-200106130341948219/providers/Microsoft.AppConfiguration/configurationStores/testaccappconf200106130341948219?api-version=2019-10-01

{
	"type": "Microsoft.AppConfiguration/configurationStores",
	"properties": {
		"provisioningState": "Creating",
		"creationDate": "2020-01-06T21:03:57.4444728+00:00",
		"endpoint": "https://testaccappconf200106130341948219.azconfig.io"
	},
	"sku": null,
	"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestRG-200106130341948219/providers/Microsoft.AppConfiguration/configurationStores/testaccappconf200106130341948219",
	"name": "testaccappconf200106130341948219",
	"location": "westeurope",
	"tags": {}
}

get https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestRG-200106130341948219/providers/Microsoft.AppConfiguration/configurationStores/testaccappconf200106130341948219?api-version=2019-10-01

{
	"type": "Microsoft.AppConfiguration/configurationStores",
	"properties": {
		"provisioningState": "Succeeded",
		"creationDate": "2020-01-06T21:03:58+00:00",
		"endpoint": "https://testaccappconf200106130341948219.azconfig.io"
	},
	"sku": {
		"name": "free"
	},
	"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestrg-200106130341948219/providers/Microsoft.AppConfiguration/configurationStores/testaccappconf200106130341948219",
	"name": "testaccappconf200106130341948219",
	"location": "westeurope",
	"tags": {
		"environment": "development"
	}
}
``

- What did you expect or want to happen?
the resource group to be returned in the correct casing as was the previous (and expected behaviour)

- How can we reproduce it?
run terraform app config tests or just do above api calls

<!--
Thanks!
-->
@katbyte katbyte changed the title Breaking change to how the appconfiguration api handles resource group names (returns in lower case now) app configuration breaking change: the api now returns the resource group name in the ID in lowercase now Jan 6, 2020
@ArcturusZhang ArcturusZhang added App Services Mgmt This issue is related to a management-plane library. Service Attention Workflow: This issue is responsible by Azure service team. labels Jan 7, 2020
@triage-new-issues triage-new-issues bot removed the triage label Jan 7, 2020
@ghost
Copy link

ghost commented Jan 7, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI

1 similar comment
@ghost
Copy link

ghost commented Jan 7, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI

@ArcturusZhang ArcturusZhang added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Jan 7, 2020
@ArcturusZhang
Copy link
Member

Hi @jimmyca could you please have a look at this?

@RickWinter RickWinter added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jul 19, 2021
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jul 19, 2021
@RickWinter RickWinter added this to the Backlog milestone Jul 19, 2021
@tadelesh
Copy link
Member

We have retired support for Azure SDK for Golang libraries which do not conform to our current Azure SDK guidelines (see announcement). Please migrate to the latest version according to the migration guide. If you could still repo this problem, please submit a support ticket in Azure directly.

@tadelesh tadelesh closed this as not planned Won't fix, can't repro, duplicate, stale Dec 26, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Mar 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
App Services bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants