-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help **fog-azure-rm** upgrade (or pin) **azure-storage** #2197
Comments
this issue has been migrated from this Tracker story: https://www.pivotaltracker.com/story/show/174179944 Please refer to that story for additional context |
Current status of this track and next steps forward@tstannard and I tried to update the fog-azure-rm gem by updating to the newest version of all the sub-dependancies for azure-storage, this resulted in a lot of failing tests and general Chaos®. After talking with @jenspinney we have decided that we should is do the minimum bump we can to get the bugfix above. This should minimize the complexity of the change. The CAPI team will reach out afterwards to the maintainers of this repo again and see if we can get traction on their side. |
@JenGoldstrich @tstannard It seems that fork is private, can you add me and @MarcPaquette as contributors? |
Just a bad link: https://github.com/tstannard/fog-azure-rm |
Seth and I submitted a PR to fog-azure-rm here to bump to the deps to 1.1, @jenspinney's idea to go from fog-arm-cf .15.preview => 1.1 was the right call! |
Bumping for the changes we submitted in [PR 438](fog/fog-azure-rm#438), which are necessary for us to bump `fog-core`. [#2197] Co-authored-by: Tom Viehman <[email protected]> Co-authored-by: Teal Stannard <[email protected]>
Bumping for the changes we submitted in [PR 438](fog/fog-azure-rm#438), which will enable us to bump `fog-core`. [#2197] Co-authored-by: Tom Viehman <[email protected]> Co-authored-by: Sarah Weinstein <[email protected]>
Bumping for the changes we submitted in [PR 438](fog/fog-azure-rm#438), which will enable us to bump `fog-core`. [#2197] Co-authored-by: Tom Viehman <[email protected]> Co-authored-by: Sarah Weinstein <[email protected]>
Bumping for the changes we submitted in [PR 438](fog/fog-azure-rm#438), which will enable us to bump `fog-core`. [#2197] Co-authored-by: Tom Viehman <[email protected]> Co-authored-by: Sarah Weinstein <[email protected]>
resolved by #2690 |
In response to the Azure regression introduced in https://github.com/cloudfoundry/capi-release/releases/tag/1.97.0
The Situation
0.15.0.preview
and1.1.0
that 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.preview
1.1.0
Deliverable: One or more of the following:
Notes:
The text was updated successfully, but these errors were encountered: