Skip to content

Remove fog AzureRM blobstore support#195

Open
WeiQuan0605 wants to merge 7 commits into
cloudfoundry:mainfrom
sap-contributions:remove-fog-azurerm-blobstore-support
Open

Remove fog AzureRM blobstore support#195
WeiQuan0605 wants to merge 7 commits into
cloudfoundry:mainfrom
sap-contributions:remove-fog-azurerm-blobstore-support

Conversation

@WeiQuan0605
Copy link
Copy Markdown

@WeiQuan0605 WeiQuan0605 commented May 26, 2026

Summary

  • Remove fog AzureRM blobstore support from capi-ci
  • Remove remaining fog AzureRM configuration from Scar environment

Related

Comment thread ci/pipeline.yml
Comment thread ci/pipeline.yml
The previous commit incorrectly removed the entire SCAR environment.
SCAR runs on Azure IaaS but only the fog AzureRM blobstore benchmark
errand should be removed. Restore all SCAR jobs and resources, keeping
the storage-cli benchmark job and removing only:
- configure-blobstore-benchmark-fog-errand.yml from scar-psql-deploy-cf ops
- use-azure-storage-blobstore.yml from scar-psql-deploy-cf ops
- ERRAND_FOG param from all three benchmark jobs (elsa-ha, olaf-mysql, scar-psql)
Scar environment is kept; only the fog AzureRM blobstore is removed.
Update README to reflect that Scar no longer uses Azure Blob Storage.
@WeiQuan0605 WeiQuan0605 requested a review from kathap May 26, 2026 18:42
Comment thread ci/pipeline.yml
Comment thread ci/pipeline.yml
Comment thread ci/pipeline.yml
Comment thread README.md
These environments use GCS and S3 respectively, which still go through
fog. Only scar-psql loses the fog errand since it used AzureRM.
This ops file configures Azure Blob Storage via storage-cli (not fog),
so it must stay after removing the fog AzureRM errand.
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.

2 participants