You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
In response to the Azure regression introduced in https://github.com/cloudfoundry/capi-release/releases/tag/1.97.0
The Situation
0.15.0.previewand1.1.0that breaks resource matching0.15.0.preview(which has the bug)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:
0.15.0.preview1.1.0Deliverable: One or more of the following:
Notes: