Pierre Prinetti

Hi :wave: What's the current status of this work? What is left to do before merging (on top of a rebase)?

Hi David, thanks for the swift answer. Looks like a nice rabbit hole for me to dig into. Thanks!

@khdegraaf Is the current Gophercloud support of fwaas sufficient for supporting your Terraform provider work? If not, can you help me understand what is missing? Thank you!

@kayrus @jtopjian If there is some outstanding work to be done in the context of this PR, would you please consider pairing with me on it, to give me a...

The test failures look related; I'm investigating those next week. I am not merging anything anyway until there's some buy-in on the general idea of adding a context at the...

> Hi, @pierreprinetti is this still on your radar? I'm still interested in this feature. Yes it is! We definitely want to land support for call-scoped context, however we will...

Note: this is a backwards-incompatible change and can't be merged without a major version bump.

I like the idea of releasing 1.0 right now; maybe with #2296 and #2297 ?

And then we take care of error returns in v2.

So, here's the proposal: 1. within the issue queue, we identify all backwards-compatible bugfixes 1. after merging all backwards-compatible fixes, we release `v1.0` 1. For v2, besides the advancements in...