Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -2042,6 +2042,17 @@
},
"subnetId": {
"type": "string",
"format": "arm-id",
"x-ms-arm-id-details": {
"allowedResources": [
{
"type": "Microsoft.Network/virtualNetworks/subnets"
},
{
"type": "Microsoft.ClassicNetwork/virtualNetworks/subnets"
Copy link
Member

@TimLovellSmith TimLovellSmith Sep 13, 2023

Choose a reason for hiding this comment

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

nonblocking question since from conservatism point of view its fine...
Is ClassicNetwork still supported? I think the plan is to deprecate it soon?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure, but I don't think it hurts to have it here as all this is really saying is that "we would accept ClassicNetwork if you give it to us" - even if you can't make new ones maybe legacy existing ones are still allowed for a while?

Agree that it might be nice to be able to remove this once it really is deprecated, though not sure how to actually accomplish that in practice when the time comes.

}
]
},
"pattern": "^/subscriptions/[^/]*/resourceGroups/[^/]*/providers/Microsoft.(ClassicNetwork|Network)/virtualNetworks/[^/]*/subnets/[^/]*$",
"description": "The full resource ID of a subnet in a virtual network to deploy the Redis cache in. Example format: /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/Microsoft.{Network|ClassicNetwork}/VirtualNetworks/vnet1/subnets/subnet1"
},
Expand Down Expand Up @@ -2601,6 +2612,14 @@
"id": {
"readOnly": true,
"type": "string",
"format": "arm-id",
"x-ms-arm-id-details": {
"allowedResources": [
{
"type": "Microsoft.Cache/redis/linkedServers"
}
]
},
"description": "Linked server Id."
}
}
Expand Down Expand Up @@ -2657,6 +2676,14 @@
"properties": {
"linkedRedisCacheId": {
"type": "string",
"format": "arm-id",
"x-ms-arm-id-details": {
"allowedResources": [
{
"type": "Microsoft.Cache/redis"
}
]
},
"description": "Fully qualified resourceId of the linked redis cache."
},
"linkedRedisCacheLocation": {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1700,6 +1700,14 @@
"properties": {
"id": {
"type": "string",
"format": "arm-id",
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we need to also add make changes in "ForceUnlinkParameters" properties, since it also have array of redis databases

Copy link
Contributor

Choose a reason for hiding this comment

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

We should I think add this attribute whenever we use arm-id for databases ARM ID.
"x-ms-arm-id-details": {
"allowedResources": [
{
"type": "Microsoft.Cache/redisEnterprise/databases"
}
]
}

Copy link
Member Author

Choose a reason for hiding this comment

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

Added the x-ms-arm-id-details here w/ entry "Microsoft.Cache/redisEnterprise/databases" and also added for ForceUnlinkParameters.

"x-ms-arm-id-details": {
"allowedResources": [
{
"type": "Microsoft.Cache/redisEnterprise/databases"
}
]
},
"x-ms-mutability": [
"read",
"create"
Expand Down Expand Up @@ -1833,7 +1841,15 @@
"ids": {
"type": "array",
"items": {
"type": "string"
"type": "string",
"format": "arm-id",
"x-ms-arm-id-details": {
"allowedResources": [
{
"type": "Microsoft.Cache/redisEnterprise/databases"
}
]
}
},
"description": "The resource IDs of the database resources to be unlinked."
}
Expand Down