Alexander Scheel

@alainchiasson @nettnikl I ran into internal pressure to do the same thing now, so I've had justification for my time, to build a design for this; see draft in https://github.com/openbao/openbao/pull/1341...

@Hoeze I think we need to rename the arch indications for RPM distros to align with `$basearch`. Goreleaser has chosen arches off of Go toolchain's preferences iirc. And I seem...

@Hoeze Yes, let me give it a spin and I'll make sure it lands before v2.3.0 GA :-)

@JanMa I'm kinda curious about this one: > output of the script committed to the repo My understanding is Git didn't perform very well with large artifacts, though I do...

I guess, I'm still confused what checking in static artifacts to a version control system would do, irrespective of method. LFS might also cost money: https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage#included-bandwidth-and-storage-per-month Based on https://tooomm.github.io/github-release-stats/?username=openbao&repository=openbao, assuming...

Hey @Hoeze -- looking into SUSE OpenBuildService more (thanks @DrDaveD!), it looks like we'd have to rebuild from source. Right now, we don't have specs at all and have goreleaser...

@tchernobog I think this is fairly easy to go add. I'd suggest a `allow_expired_cert_revocation` field to `config/crl` and the behavior changes, but also add a new field `revoked_safety_buffer` to default...

Cool! Let me know if you have questions.

@fatima2003 Yes, this is the expected behavior. All operations are meant to be repeatable; e g., if you delete a secret in KV and then redo that, it'll also report...

@DanGhita Sorry, I got distracted! Right, my assumption was both were either in separate Bao instances. In particular, if you were looking to build a hierarchical Bao setup (say, you...