You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"ScheduledEventsPolicy": {
"properties": {
"userInitiatedRedeploy": {
"$ref": "#/definitions/UserInitiatedRedeploy",
"description": "The configuration parameters used while creating userInitiatedRedeploy scheduled event setting creation."
},
"userInitiatedReboot": {
"$ref": "#/definitions/UserInitiatedReboot",
"description": "The configuration parameters used while creating userInitiatedReboot scheduled event setting creation."
}
}
"UserInitiatedRedeploy": {
"properties": {
"automaticallyApprove": {
"type": "boolean",
"description": "Specifies Redeploy Scheduled Event related configurations."
}
}
}
"UserInitiatedReboot": {
"properties": {
"automaticallyApprove": {
"type": "boolean",
"description": "Specifies Reboot Scheduled Event related configurations."
}
}
}
These two property models both have only one property called automaticallyApprove. If there is only one property, we will flatten this property out. Now there will be two properties called automaticallyApprove.
Current solution is, in .net autorest.md, we have
# Add a dummy property because generator tries to flatten automaticallyApprove in both UserInitiatedRedeploy and UserInitiatedReboot
- from: computeRPCommon.json
where: $.definitions.UserInitiatedRedeploy.properties
transform: >
$.dummyProperty = {
"type": "string",
"description": "This is a dummy property to prevent flattening."
};
Now the problem is, when we migrate to TypeSpec, how we are going to add this configuration.
The text was updated successfully, but these errors were encountered:
Take compute as an example:
These two property models both have only one property called
automaticallyApprove
. If there is only one property, we will flatten this property out. Now there will be two properties calledautomaticallyApprove
.Current solution is, in .net autorest.md, we have
Now the problem is, when we migrate to TypeSpec, how we are going to add this configuration.
The text was updated successfully, but these errors were encountered: