Skip to content

[Blueprints] Add published blueprint object to the payload to support change notes #6399

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.

Sign up for GitHub

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

Merged
sergey-shandar merged 1 commit into from
Jun 25, 2019
Merged

[Blueprints] Add published blueprint object to the payload to support change notes #6399

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions .../resource-manager/Microsoft.Blueprint/preview/2018-11-01-preview/blueprintDefinition.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -416,6 +416,15 @@
},
{
"$ref": "#/parameters/PublishedBlueprintVersionIdParameter"
},
{
"name": "publishedBlueprint",
"in": "body",
"required": false,
"schema": {
"$ref": "#/definitions/PublishedBlueprint"
},
"description": "Published Blueprint to create or update."
}
Copy link
Member

@majastrz majastrz Jun 21, 2019 •
edited
Loading

Choose a reason for hiding this comment

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

Note for other reviewers:
The blueprint backend has always supported this and it was always optional. So SDKs generated from swaggers with and without this change will work just fine. #ByDesign

],
"responses": {
Expand Down