a util that can parse arm id

[yukun-dong]

Is your feature request related to a problem? Please describe.
If I want to get a machine learning workspace using a workspace id. I need to extract the subscriptionId, resourcegroup,workspacename from the id first then use js sdk to get it. In this case it would be helpful if there is a util that can parse the id for me.

The .net and go sdk already has a util resourceIdentifier that can help parse the arm id but js doesn't.

Describe the solution you'd like
The js sdk has a util just like resourceIdentifier.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[xirzec]

@yukun-dong so I can route your request correctly, can you confirm what package you are using? Is it @azure/arm-machinelearning?

[github-actions]

Hi @yukun-dong. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[qiaozha]

@xirzec this is actually a core-util requirement, it will provide a helper to our customer that takes a resource id as input and output the subscriptionId, resourceGroupName, resourceName etc. similar like https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/azcore/arm/internal/resource/resource_identifier.go This is a common request in ARM libraries, but are you okay with putting this into core-util?

[jeremymeng]

Related to this? #30678

[xirzec]

@xirzec this is actually a core-util requirement, it will provide a helper to our customer that takes a resource id as input and output the subscriptionId, resourceGroupName, resourceName etc. similar like https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/azcore/arm/internal/resource/resource_identifier.go This is a common request in ARM libraries, but are you okay with putting this into core-util?

Seems reasonable to me, would we want ARM packages to re-export this helper for convenience? I know we usually avoid asking customers to directly import from core.