Remove single service restriction arm #3572
Conversation
timotheeguerin
added
the
int:azure-specs
microsoft-github-policy-service
bot
added
the
lib:azure-resource-manager
commit: |
|
All changed packages have been documented.
Show changes
|
|
You can try these changes here
|
| @armProviderNamespace | ||
| namespace Microsoft.ServiceA { | ||
| model ResA is TrackedResource<{}> { | ||
| @key @segment("foos") @path name: string; | ||
| } | ||
| } | ||
| @armProviderNamespace | ||
| namespace Microsoft.ServiceB { | ||
| model ResB is TrackedResource<{}> { | ||
| @key @segment("foos") @path name: string; | ||
| } | ||
| } | ||
| `); |
There was a problem hiding this comment.
so how would it behave if we have two parts with the same provider namespace but with different api version enum? this case happen in compute.
Do we have to do something like this?
@providerNamespace("Microsoft.Compute")
@versioned(VMVersions)
namespace Microsoft.Compute.Vms {}
@providerNamespace("Microsoft.Compute")
@versioned(DiskVersions)
namespace Microsoft.Compute.Disks {}
and if we have to do it in the above way, we might not be able to just put them into the one client.tsp without changing their specs.
There was a problem hiding this comment.
yeah that would be how to do it I asssume playground
| } | ||
| `); | ||
|
|
||
| const resources = getArmResources(program); |
There was a problem hiding this comment.
I think there is a plan that we deprecate this API.
Should we use resolveArmResources instead?
There was a problem hiding this comment.
hhm maybe but this is what all the tests in this file are using and I don't think it will fully go away(at least internally) as this is just the low level accessor
3 participants
fix #3555