[AutoPR storagecache/resource-manager/v2019_11_01] [Mirror] Microsoft Azure StorageCache - Add 204 response code to cache flush, start, stop and upgrade operation.

[openapi-bot-ppe]

Created to sync test-repo-billy/azure-rest-api-specs#377

Installation Instructions

You can install the package storagecache/resource-manager/v2019_11_01 of this PR by downloading the artifact jar files. Then ensure that the jar files are on your project's classpath.

Direct Download

The generated package artifacts can be directly downloaded from here:

• pom.xml
• azure-mgmt-storagecache-1.0.0-beta-javadoc.jar
• azure-mgmt-storagecache-1.0.0-beta-sources.jar
• azure-mgmt-storagecache-1.0.0-beta.jar

[github-actions]

Hi @openapi-bot-ppe[bot]. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @openapi-bot-ppe[bot]. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @openapi-bot-ppe[bot]. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @openapi-bot-ppe[bot]. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.