Alexander Scheel

Results 217 comments of Alexander Scheel

Synicng some discussion from Matrix earlier: To remove HashiCorp branding, we ~will need to fork https://github.com/hashicorp/design-system~ have forked https://github.com/openbao/design-system -- this is dep'd from https://github.com/openbao/openbao/blob/main/ui/package.json#L63 -> https://www.npmjs.com/package/@hashicorp/flight-icons -> https://github.com/hashicorp/design-system/tree/main/packages/ember-flight-icons We...

@rhuddleston IIRC, the issue is the design repo itself has HashiCorp logos &c that are used by OpenBao's UI. So without forking it, our only option would be to ask...

Go for it if you think it's doable! I will confess my frontend experience is quite minimal and limited to carefully supervised attempts. :D I have a little more familiarity...

Thanks for the PR @David-Langan! @JanMa I think has addressed this everywhere in #397 so I'm going to go ahead and close this.

@sagikazarmark Have you had a chance to look at #64? Will it affect your project much, to move the non-OSI integrations to external plugins? Is Raft OK for a storage...

@sagikazarmark Apologies, I just now realized we never replied to this last item. Our meetings our held on Thursdays at 11AM Eastern: https://openbao.org/docs/contributing/#community-calls

I believe these are based on OpenAPI specs... Migrating our bespoke API docs over to something autogenerated like these language libraries would likely help to catch bugs.

At GitLab, we're interested in a Ruby client. It looks like upstream is in the process of [deprecating theirs](https://github.com/hashicorp/vault-ruby/pull/336), so we'd be interested in maintaining an OpenAPI generated Ruby client...

The one issue with long-running GETs is that the core occasionally needs to shut down for various reasons. One of these is the seal mechanism, but other various state changes...

Thinking about this a bit more, what ends up happening at the GRPC layer for long-running GET requests (I believe) is an indication of a request (client->server->plugin), and the plugin...