updating redis spec after changes to the converter #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @amarzavery, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution! TTYL, AZPRBOT; |
amarzavery
added a commit
that referenced
this pull request
Nov 4, 2015
updating redis spec after changes to the converter
matthchr
pushed a commit
to matthchr/azure-rest-api-specs
that referenced
this pull request
May 9, 2017
New Swagger of Microsoft.Consumption and new version of Microsoft.Billing
yuwzho
pushed a commit
that referenced
this pull request
Dec 20, 2021
raych1
pushed a commit
that referenced
this pull request
Dec 22, 2021
…API version 2022-01-01-preview (#17141) * copy from last api version * Add system data and example * Add availability zones change * Configuration Service * Service Registry * Gateway * API portal * App and Deployment * BuildServices/Builds/Builders/BuildResults * BuildPackBindings * fix swagger of build service (#43) * fix swagger of build service * fix * fix: add agentPool in BuildProperties (#44) * Add fqdn in service resource (#45) Co-authored-by: Xiaoyun Ding <xiading@microsoft.com> * Change appName to appResourceId (#46) * Change appName to appResourceId * fix * Add resource id to connect resources * Change operatorRuntimeState to resourceRequest (#49) * Change appName to appResourceId * rename sourceGateways to gatewayIds * Change operatorRuntimeState to resourceRequest * feat: update agent pool swagger (#50) * Update 201 descriptions about header * add get build (#51) * Remove 202 for PUT * List and Get supportedBuildpacks * set active deployment should be async * Update setActiveDeployments response body * ContentCertificateProperties.content should be secret * Add jvmOptions for Jar type Co-authored-by: Qingyi Liu <34502364+smile37773@users.noreply.github.com> Co-authored-by: Xiaoyun Ding <leonard520@users.noreply.github.com> Co-authored-by: Xiaoyun Ding <xiading@microsoft.com> Co-authored-by: ninpan-ms <71061174+ninpan-ms@users.noreply.github.com> Co-authored-by: zhoufenqin <fenzho@microsoft.com>
LeiWang3
pushed a commit
to LeiWang3/azure-rest-api-specs
that referenced
this pull request
Mar 31, 2022
…API version 2022-01-01-preview (Azure#17141) * copy from last api version * Add system data and example * Add availability zones change * Configuration Service * Service Registry * Gateway * API portal * App and Deployment * BuildServices/Builds/Builders/BuildResults * BuildPackBindings * fix swagger of build service (Azure#43) * fix swagger of build service * fix * fix: add agentPool in BuildProperties (Azure#44) * Add fqdn in service resource (Azure#45) Co-authored-by: Xiaoyun Ding <xiading@microsoft.com> * Change appName to appResourceId (Azure#46) * Change appName to appResourceId * fix * Add resource id to connect resources * Change operatorRuntimeState to resourceRequest (Azure#49) * Change appName to appResourceId * rename sourceGateways to gatewayIds * Change operatorRuntimeState to resourceRequest * feat: update agent pool swagger (Azure#50) * Update 201 descriptions about header * add get build (Azure#51) * Remove 202 for PUT * List and Get supportedBuildpacks * set active deployment should be async * Update setActiveDeployments response body * ContentCertificateProperties.content should be secret * Add jvmOptions for Jar type Co-authored-by: Qingyi Liu <34502364+smile37773@users.noreply.github.com> Co-authored-by: Xiaoyun Ding <leonard520@users.noreply.github.com> Co-authored-by: Xiaoyun Ding <xiading@microsoft.com> Co-authored-by: ninpan-ms <71061174+ninpan-ms@users.noreply.github.com> Co-authored-by: zhoufenqin <fenzho@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.