Rémi Lapeyre

HI @jefferai, > That said, I also don't think it necessarily matters, as Boundary will never round trip a secret value set from Terraform back in a read. This is...

Hi @jefferai, I initially tried to base the generator on the protobufs but I found it more difficult to get it working than basing the generator on the OpenAPI, I...

Also regarding Boundary and Terraform, but this time to make it possible to use Boundary proxies from Terraform I opened https://github.com/hashicorp/terraform/pull/29402 that may interest you.

Hi @jefferai, sorry to answer this late, I've had a lot of work this week. I thought about both options and I don't have a strong preference for either, it...

Hi everyone, sorry for the delay for getting back I've had a lot of work last weeks. I've been looking into converting the current generator from using the swagger definition...

Thanks fr the ping @hsimon-hashicorp

Thanks for letting me know. To give more context this is a secret engine that was asked to us by a Vault Enterprise client. Since it is also one of...

Hi @xeroc, as you already noticed `vault-acme` does not reproduce the API of the PKI engine. I first chose this because creating certificates with an ACME provider is quite different...

Hi @rellerreller everything you reported is correct and that behavior was set a very long time ago. The issue now is that fixing it would break backward compatibility. That ID...

> Hi @remilapeyre, thanks for this submission! I assume this is still a valid and reasonable thing to want from backend migration output. I will raise it with the team...