-
Notifications
You must be signed in to change notification settings - Fork 368
Closed
Description
In response to the Azure regression introduced in https://github.com/cloudfoundry/capi-release/releases/tag/1.97.0
The Situation
- CC uses fog-azure-rm for communicating with Azure blobstores
- fog-azure-rm uses azure-storage under the hood
- azure-storage has a bug between
0.15.0.previewand1.1.0that breaks resource matching - We use a cf-specific branch of fog-azure-rm
- That branch depends on azure-storage < 1.0, so Bundler keeps trying to upgrade azure-storage to
0.15.0.preview(which has the bug) - Master of fog-azure-rm is pinned to an even older version of azure-storage
To Do
Ideally bundler (and dependabot) shouldn't try to upgrade us to a broken version of fog-azure-rm. It would also be cool if in the future we could move to newer versions of fog-azure-rm and azure-storage for new features and security fixes.
Some possible paths forward:
- Move to the mainline releases of fog-azure-rm, assuming it has the features we need from our special branch
- Convince the fog-azure-rm maintainers to pin fog-storage on our special branch to a version <
0.15.0.preview - Convince the fog-azure-rm maintainers to bump fog-storage on our special branch to a version >=
1.1.0 - Some other, even better, plan
Deliverable: One or more of the following:
- A github issue against fog-azure-rm
- A github PR against fog-azure-rm
- A change to the version of the fog-azure-rm that CC uses
Notes:
- If relevant, you can deliver this story when the issue or PR is submitted. No need to wait for the issue/PR to be resolved.
- There is currently a PR for bumping azure-storage in fog-azure-rm
- Related issue: Cf push times out on azure #1846
Metadata
Metadata
Assignees
Labels
No labels