Skip to content

Update Azure Storage blobstore documentation#214

Merged
anita-flegg merged 3 commits intocloudfoundry:masterfrom
sap-contributions:azure_storage-cli
Feb 17, 2026
Merged

Update Azure Storage blobstore documentation#214
anita-flegg merged 3 commits intocloudfoundry:masterfrom
sap-contributions:azure_storage-cli

Conversation

@jochenehret
Copy link
Contributor

  • the Fog implementation is deprecated and will be removed
  • describe new Storage CLI configuration

* the Fog implementation is deprecated and will be removed
* describe new Storage CLI configuration
stephanme
stephanme previously approved these changes Feb 13, 2026
@stephanme
Copy link
Member

If you want to configure your blobstore manually, see the topics below for guidance.

The Cloud Controller has four types of objects that need to be stored in a blobstore: <code>buildpacks</code>, <code>droplets</code>, <code>packages</code>, and <code>resource_pool</code>. By default, the blobstore configuration uses the Fog Ruby gem, but can also use the WebDAV protocol.
The Cloud Controller has four types of objects that need to be stored in a blobstore: <code>buildpacks</code>, <code>droplets</code>, <code>packages</code>, and <code>resource_pool</code>. By default, the blobstore configuration uses the Fog Ruby gem, but can also use the WebDAV protocol. Note that the Ruby Fog implementation is deprecated and will be gradually replaced with the new [`Storage CLI`](https://github.com/cloudfoundry/storage-cli) implementations.
Copy link
Contributor

Choose a reason for hiding this comment

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

This paragraph uses both "Fog Ruby" and "Ruby Fog." Are both correct?
And if it's deprecated, is it really still the default?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm changing "Fog Ruby" to "Ruby Fog". For now, the Fog implementation is considered the default. We are replacing Fog with the new "storage-cli" implementation step-by-step and eventuall we'll remove Fog entirely.

If you want to configure your blobstore manually, see the topics below for guidance.

The Cloud Controller has four types of objects that need to be stored in a blobstore: <code>buildpacks</code>, <code>droplets</code>, <code>packages</code>, and <code>resource_pool</code>. By default, the blobstore configuration uses the Fog Ruby gem, but can also use the WebDAV protocol.
The Cloud Controller has four types of objects that need to be stored in a blobstore: <code>buildpacks</code>, <code>droplets</code>, <code>packages</code>, and <code>resource_pool</code>. By default, the blobstore configuration uses the Ruby Fog gem, but can also use the WebDAV protocol. Note that the Ruby Fog implementation is deprecated and will be gradually replaced with the new [`Storage CLI`](https://github.com/cloudfoundry/storage-cli) implementations.
Copy link
Contributor

Choose a reason for hiding this comment

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

What I mean is -- if it's deprecated, why is it still the default?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well because the transition to the new "storage-cli" implementation is still ongoing. Only for some hyperscalers (AliCloud, Azure) the "storage-cli" implementation is rolled out. For the others, the Ruby Fog implementation is still the default.

Copy link
Contributor

Choose a reason for hiding this comment

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

To me, deprecated means "no longer supported"/"don't use," so still being default doesn't make sense.

How about wording it something like this:

The new storage-cli solution is being rolled out across the various hyperscalers (AliCloud and Azure, for example, so the Ruby Fog gem is still the default for some hyperscalers.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well there are different interpretations of "deprecated". In our case it means "no longer actively developed" and "has outdated dependencies", but is still working. So in lack of a replacement, Ruby Fog is still the default for many providers.

But I'll rephrase the paragraph.

@anita-flegg anita-flegg merged commit 93d5720 into cloudfoundry:master Feb 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants