-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix swagger correctness #4
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4762,7 +4762,7 @@ | |
"additionalProperties": { | ||
"type": "string" | ||
}, | ||
"maxItems": 1000 | ||
"maxItems": 50 | ||
}, | ||
"state": { | ||
"description": "Identifies the state of an invoice section.", | ||
|
@@ -4782,6 +4782,14 @@ | |
"type": "string", | ||
"readOnly": true | ||
}, | ||
"tags": { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What is the difference between tags and labels? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They are the same. Plan was to eliminate one, but now both are being returned and this is causing s360 to flag this. So to fix this issue in GA, i am adding tags also to the swagger spec. |
||
"type": "object", | ||
"description": "Dictionary of metadata associated with the invoice section.", | ||
"additionalProperties": { | ||
"type": "string" | ||
}, | ||
"maxItems": 50 | ||
}, | ||
"targetCloud": { | ||
"description": "Identifies the cloud environments that are associated with an invoice section. This is a system managed optional field and gets updated as the invoice section gets associated with accounts in various clouds.", | ||
"$ref": "#/definitions/TargetCloud", | ||
|
@@ -5332,6 +5340,12 @@ | |
"$ref": "#/definitions/Product" | ||
} | ||
}, | ||
"totalCount": { | ||
"description": "Total number of records.", | ||
"type": "number", | ||
"format": "int32", | ||
"readOnly": true | ||
}, | ||
"nextLink": { | ||
"description": "The link (url) to the next page of results.", | ||
"type": "string", | ||
|
@@ -5679,6 +5693,14 @@ | |
"description": "The sku description of the Azure plan for the subscription.", | ||
"type": "string", | ||
"readOnly": true | ||
}, | ||
"suspensionReasons": { | ||
"description": "The suspension reason for a subscription. Applies only to subscriptions in Microsoft Online Services Program (MOSP) billing accounts.", | ||
"type": "array", | ||
"readOnly": true, | ||
"items": { | ||
"type": "string" | ||
} | ||
} | ||
} | ||
}, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -63,7 +63,8 @@ | |
"billingProfileDisplayName": "Contoso operations billing" | ||
} | ||
} | ||
] | ||
], | ||
"totalCount": 2 | ||
} | ||
} | ||
} | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -64,7 +64,8 @@ | |
"billingProfileDisplayName": "Contoso operations billing" | ||
} | ||
} | ||
] | ||
], | ||
"totalCount": 2 | ||
} | ||
} | ||
} | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,7 +68,8 @@ | |
"billingProfileDisplayName": "Contoso operations billing" | ||
} | ||
} | ||
] | ||
], | ||
"totalCount": 2 | ||
} | ||
} | ||
} | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -64,7 +64,8 @@ | |
"billingProfileDisplayName": "Contoso operations billing" | ||
} | ||
} | ||
] | ||
], | ||
"totalCount": 2 | ||
} | ||
} | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have validation on key/value lengths as well, like ARM does? We need to make sure that we scale properly when someone creates the largest possible invoice section entities, many times.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we have validation on key/value lengths as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should describe the validation in the description of this property so people can look this up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added