Brian Scholer

This looks really useful.. any movement on this?

Hi @xunzhou , Similar to #874: The `hvac` project is simplifying its developer workflow and removing the `develop` branch. Please be aware for future PRs that the project's default branch...

Hi @sknopp , are you still having this issue? The exception being raised is directly based on the response being received from the Vault server, so I'm not sure if...

Hello again @dosisod ! First I want to say thanks for the detailed explanation, and especially for splitting the changes per-rule into discrete commits, that's exactly how I would've liked...

There are a bunch of (our) deprecation warnings around the MFA class: https://github.com/hvac/hvac/actions/runs/6138188913/job/16654830995#step:7:77 These should be resolved when #1026 is resolved.

@dosisod thanks for raising this! I did some cursory investigation but couldn't find anything just yet so I split it off to a new issue to track it.

Thanks for following up @dosisod . Maybe the quickest change we could make there is choosing non-standard ports. I think we already even have a helper function in the project...

> > Hopefully there's existing tests and documentation you could extend (I haven't looked yet); if not I understand that adding it from scratch could be a burden. > >...

The artifact upload/download actions are tightly coupled and must be updated together, either in a new PR or as commits added to one of these. It may also require workflow...

The artifact upload/download actions are tightly coupled and must be updated together, either in a new PR or as commits added to one of these. It may also require workflow...