-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add xms-ids for mediaservices #17742
Changes from 1 commit
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 |
---|---|---|
|
@@ -187,6 +187,9 @@ | |
"items": { | ||
"$ref": "#/definitions/MetricDimension" | ||
}, | ||
"x-ms-identifiers": [ | ||
"name" | ||
], | ||
"description": "The metric dimensions.", | ||
"readOnly": true | ||
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. Same here MediaServiceProperties - > storageAccounts is also an array. does this not need x-ms-idenitfiers. Can you explain a little on which scenario should we be adding this new property? 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. The type object of storageAccounts, which is sotrageAccount in this case, has a property named "id" already, which is the default value expected when x-ms-identifiers is not specified. Same reason for AccountFilterCollection. Hope this helps :) |
||
}, | ||
|
@@ -236,6 +239,9 @@ | |
"items": { | ||
"$ref": "#/definitions/LogSpecification" | ||
}, | ||
"x-ms-identifiers": [ | ||
"name" | ||
], | ||
"description": "List of log specifications.", | ||
"readOnly": true | ||
}, | ||
|
@@ -244,6 +250,9 @@ | |
"items": { | ||
"$ref": "#/definitions/MetricSpecification" | ||
}, | ||
"x-ms-identifiers": [ | ||
"name" | ||
], | ||
"description": "List of metric specifications.", | ||
"readOnly": true | ||
} | ||
|
@@ -754,6 +763,9 @@ | |
"items": { | ||
"$ref": "#/definitions/Operation" | ||
}, | ||
"x-ms-identifiers": [ | ||
"name" | ||
], | ||
"description": "A collection of Operation items." | ||
} | ||
}, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -362,6 +362,9 @@ | |
"items": { | ||
"$ref": "#/definitions/H265Layer" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
], | ||
"description": "The collection of output H.265 layers to be produced by the encoder." | ||
} | ||
}, | ||
|
@@ -552,6 +555,7 @@ | |
"items": { | ||
"$ref": "#/definitions/TrackDescriptor" | ||
}, | ||
"x-ms-identifiers": [], | ||
"description": "The list of TrackDescriptors which define the metadata and selection of tracks in the input." | ||
} | ||
}, | ||
|
@@ -1037,6 +1041,9 @@ | |
"items": { | ||
"$ref": "#/definitions/Overlay" | ||
}, | ||
"x-ms-identifiers": [ | ||
"inputLabel" | ||
], | ||
"description": "The properties of overlays to be applied to the input video. These could be audio, image or video overlays." | ||
} | ||
}, | ||
|
@@ -1220,6 +1227,9 @@ | |
"items": { | ||
"$ref": "#/definitions/H264Layer" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
], | ||
"description": "The collection of output H.264 layers to be produced by the encoder." | ||
} | ||
}, | ||
|
@@ -1239,6 +1249,9 @@ | |
"items": { | ||
"$ref": "#/definitions/JpgLayer" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
], | ||
"description": "A collection of output JPEG image layers to be produced by the encoder." | ||
}, | ||
"spriteColumn": { | ||
|
@@ -1280,6 +1293,7 @@ | |
"items": { | ||
"$ref": "#/definitions/OutputFile" | ||
}, | ||
"x-ms-identifiers": [], | ||
"description": "The list of output files to produce. Each entry in the list is a set of audio and video layer labels to be muxed together ." | ||
} | ||
}, | ||
|
@@ -1326,6 +1340,9 @@ | |
"items": { | ||
"$ref": "#/definitions/PngLayer" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
], | ||
"description": "A collection of output PNG image layers to be produced by the encoder." | ||
} | ||
}, | ||
|
@@ -1471,13 +1488,17 @@ | |
"items": { | ||
"$ref": "#/definitions/Codec" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
], | ||
"description": "The list of codecs to be used when encoding the input video." | ||
}, | ||
"formats": { | ||
"type": "array", | ||
"items": { | ||
"$ref": "#/definitions/Format" | ||
}, | ||
"x-ms-identifiers": [], | ||
"description": "The list of outputs to be produced by the encoder." | ||
} | ||
}, | ||
|
@@ -1755,6 +1776,7 @@ | |
"items": { | ||
"$ref": "#/definitions/TransformOutput" | ||
}, | ||
"x-ms-identifiers": [], | ||
"description": "An array of one or more TransformOutputs that the Transform should generate." | ||
} | ||
}, | ||
|
@@ -1831,6 +1853,7 @@ | |
"items": { | ||
"$ref": "#/definitions/InputDefinition" | ||
}, | ||
"x-ms-identifiers": [], | ||
"description": "Defines a list of InputDefinitions. For each InputDefinition, it defines a list of track selections and related metadata." | ||
} | ||
}, | ||
|
@@ -1904,6 +1927,7 @@ | |
"items": { | ||
"$ref": "#/definitions/JobInput" | ||
}, | ||
"x-ms-identifiers": [], | ||
"description": "List of inputs to a Job." | ||
} | ||
}, | ||
|
@@ -2176,6 +2200,9 @@ | |
"items": { | ||
"$ref": "#/definitions/JobErrorDetail" | ||
}, | ||
"x-ms-identifiers": [ | ||
"code" | ||
], | ||
"description": "An array of details about specific errors that led to this reported error.", | ||
"readOnly": true | ||
} | ||
|
@@ -2296,6 +2323,9 @@ | |
"items": { | ||
"$ref": "#/definitions/JobOutput" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
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. label in the definition and a few other places, is not a required property. does it make sense to keep the array empty here? 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. Yeah totally. If there is no property can be used as an identifier, we can keep the x-ms-identifiers array empty. 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. I have pushed a new commit for removing the not required label property from xms-ids. Please take a look. 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. Is this change needed urgently? all our swaggers are auto generated from code. If we make this change now directly to swagger, in the next release, I have to manually manage these. I rather they be added in our service code, so they are added properly. Another question, is changing these identifiers considered breaking change? 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. The check for x-ms-identifiers will be turned on after the whole initial work is done. I am sorry that this may add more work to you. @yantang-msft this could be a generic problem for teams that auto-generate their swaggers. What would be your suggestions on this? AFAIK, changing these identifiers in the future should not be a breaking change. 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. Hi @giakas, I checked with my team and unfortunately you team would probably have to manually add these annotations to the autogenerated swagger next time you generate them, or update the code generation tool to include this new annotation, which are what some other teams that have autogenerated swagger will be doing. I think for now we can check in this change first if you don't have any more code change request, which eliminates any unexpected error around x-ms-identifiers of your swaggers, and if you have any concerns or suggestions about how to make the work |
||
], | ||
"description": "The outputs for the Job." | ||
}, | ||
"priority": { | ||
|
@@ -2367,6 +2397,9 @@ | |
"items": { | ||
"$ref": "#/definitions/JobInputClip" | ||
}, | ||
"x-ms-identifiers": [ | ||
"label" | ||
], | ||
"description": "JobInputs that make up the timeline." | ||
} | ||
}, | ||
|
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.
There is one more array in this file, AccountFilterCollection->value. does this not need x-ms-identifiers?