Skip to content

Help **fog-azure-rm** upgrade (or pin) **azure-storage** #2197

@sethboyles

Description

@sethboyles

In response to the Azure regression introduced in https://github.com/cloudfoundry/capi-release/releases/tag/1.97.0

The Situation

  1. CC uses fog-azure-rm for communicating with Azure blobstores
  2. fog-azure-rm uses azure-storage under the hood
  3. azure-storage has a bug between 0.15.0.preview and 1.1.0 that breaks resource matching
  4. We use a cf-specific branch of fog-azure-rm
  5. 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)
  6. 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:

  1. Move to the mainline releases of fog-azure-rm, assuming it has the features we need from our special branch
  2. Convince the fog-azure-rm maintainers to pin fog-storage on our special branch to a version < 0.15.0.preview
  3. Convince the fog-azure-rm maintainers to bump fog-storage on our special branch to a version >= 1.1.0
  4. Some other, even better, plan

Deliverable: One or more of the following:

  1. A github issue against fog-azure-rm
  2. A github PR against fog-azure-rm
  3. A change to the version of the fog-azure-rm that CC uses

Notes:

  1. 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.
  2. There is currently a PR for bumping azure-storage in fog-azure-rm
  3. Related issue: Cf push times out on azure #1846

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions