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

[Recovery Services] ProtectedItemsClient returns some azure resource ID's with Subscriptions capitalized. #2824

Closed
katbyte opened this issue Sep 26, 2018 · 20 comments
Assignees
Labels
Blocked 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. Recovery Services Backup Service Attention This issue is responsible by Azure service team.

Comments

@katbyte
Copy link

katbyte commented Sep 26, 2018

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/recoveryservices/mgmt/2016-06-01/backup"
  • SDK version e.g. master, latest, 18.1.0
{
			"checksumSHA1": "XiQW2U5GBOhOfPTwFlFeM2thDCs=",
			"path": "github.com/Azure/azure-sdk-for-go/services/recoveryservices/mgmt/2016-06-01/backup",
			"revision": "2935c0241c74bd8549b843978dd6fc1be6f48b4a",
			"revisionTime": "2018-08-31T14:25:13Z",
			"version": "=v20.1.0",
			"versionExact": "v20.1.0"
		},
  • output of go version
  • What happened?
    backup.ProtectedItemsClient returns its response.ID and response.Properties.PolicyID in an unexpected format, Subscriptions is unexpectedly capitalized. This stands out as the protection policy client returns ID's as lowercase so when using it as an input to this client a different value is returned.

  • What did you expect or want to happen?
    id returned with subscription in lower case

  • How can we reproduce it?

  • Anything we should know about your environment.

@jhendrixMSFT
Copy link
Member

@sumitmal can you please comment on this?

@mozehgir mozehgir added the Service Attention This issue is responsible by Azure service team. label Sep 26, 2018
@katbyte
Copy link
Author

katbyte commented Oct 24, 2018

@marstr, any updates on this one?

@marstr
Copy link
Member

marstr commented Oct 24, 2018

I have a thread going internally. I'm still being routed to the correct owner, so no update yet.

@tombuildsstuff
Copy link
Contributor

@jhendrixMSFT - is there any update here? :)

@jhendrixMSFT
Copy link
Member

@tombuildsstuff looks like the email thread died. :( Working on it...

@pvrk
Copy link
Member

pvrk commented May 28, 2019

@katbyte, @tombuildstuff: I want to understand, if the sequence failing because the Subscription is returned in uppercase? Because this issue is marked as blocked, I want to understand more on this scenario. Adding @AditTulasi for information.

@pvrk
Copy link
Member

pvrk commented May 28, 2019

#customer-response-expected

@pvrk
Copy link
Member

pvrk commented Jun 6, 2019

#please-close
since we didn't receive a response. Can re-open if the sequence is failing.

@katbyte
Copy link
Author

katbyte commented Jun 11, 2019

This is still an issue @pvrk. Yes this causes issues and other APIs to fail because they expect subscriptions to be lowercase and we are getting it as uppercase.

@katbyte
Copy link
Author

katbyte commented Aug 4, 2019

@pvrk, @jhendrixMSFT, any progress on this? we have another PR that has uncovered many many more case differences with the recovery services API: https://github.com/terraform-providers/terraform-provider-azurerm/pull/4003/files

@pvrk
Copy link
Member

pvrk commented Sep 5, 2019

@TAdityaAnirudh: can you please check this?

@adit-t
Copy link

adit-t commented Sep 18, 2019

Thanks for the clarification @katbyte . We will fix it in upcoming release.

Out of curiosity, why are those APIs expecting Subscription ID in lower case only? Shouldn't we be fixing those APIs instead of updating every other response?

@katbyte
Copy link
Author

katbyte commented Sep 18, 2019

@TAdityaAnirudh & @pvrk, most if not every other azure api we work with returns it in lowercase (or expects it to be). recovery services seems to be the exception here so it stands to reason recovery services should change to be consistent with the rest of azure.

@adit-t
Copy link

adit-t commented Sep 24, 2019

Fix has been checked-in. It should be deployed by end of November.

@katbyte
Copy link
Author

katbyte commented Sep 27, 2019

Thanks @TAdityaAnirudh!

@pvrk
Copy link
Member

pvrk commented Dec 9, 2019

@katbyte : Now, the subscription ID is returned in lower case and for all other resource IDs, case is preserved. I hope I can close this issue.

@katbyte
Copy link
Author

katbyte commented Dec 18, 2019

Hi @pvrk, it looks like the azure file share backup APIs are still returning subscription in the wrong case. Was it fixed for all api endpoints? do we need to upgrade to a newer version of the API?

@pvrk
Copy link
Member

pvrk commented Dec 31, 2019

@katbyte : Thanks for the feedback. Will check and let you know.

@ArcturusZhang ArcturusZhang added customer-reported Issues that are reported by GitHub users external to the Azure organization. and removed customer labels Jan 9, 2020
@pvrk pvrk self-assigned this Mar 10, 2020
@pvrk
Copy link
Member

pvrk commented Mar 13, 2020

@katbyte : We internally checked once more and saw that the fix is present even for AFS APIs. Can you please provide any particular API where you are still seeing the wrong case behavior?

@tzhanl tzhanl added the Mgmt This issue is related to a management-plane library. label Aug 25, 2020
@tzhanl tzhanl added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Aug 25, 2020
@pvrk
Copy link
Member

pvrk commented Dec 28, 2020

Closing this bug due to lack of response. We have checked internally once again and doesn't see this issue getting re-produced after the fix was provided.

@pvrk pvrk closed this as completed Dec 28, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Blocked 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. Recovery Services Backup Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

10 participants