Add AliOSS storage-cli support in capi-release #593
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.
Thanks for contributing to the
capi_release. To speed up the process of reviewing your pull request please provide us with:A short explanation of the proposed change:
This change adds AliCloud OSS support via storage-cli to capi-release.
An explanation of the use cases your change solves
Allows Cloud Foundry deployments using AliCloud OSS to migrate from the legacy fog-aliyun implementation to the newer storage-cli backend.
Provides a consistent storage-cli integration story across multiple IaaS providers (AzureRM and Aliyun), simplifying configuration and operational tooling.
Avoids relying on the outdated fog-aliyun gem and its old transitive dependencies, reducing maintenance and security risk for operators running CF on AliCloud.
Links to any other associated PRs
https://github.com/cloudfoundry/storage-cli
Azure storage-cli integration #580
I have viewed signed and have submitted the Contributor License Agreement
I have made this pull request to the
developbranchI have run CF Acceptance Tests on bosh lite