Vault Backend - Namespace support

[RossKohler]

Hi,

In the documentation for configuring Vault as a secrets backend here it's mentioned that all the ENV variables supported by Vault here are also supported by the operator. I'm trying to interface with Vault Enterprise which has a concept of 'namespaces' so when I try and retrieve connections and variables I need the client to look within a specific namespace i.e. 'dev'. I'm finding that the backend operator is not respecting my `VAULT_NAMESPACE' env variable which I'm setting and thus the request the client is making is not using the correct URL. The URL is missing a namespace component. Is there any way I can get this to work?

In HVAC I have validated that my configuration works if the namespace is explicitly passed to the client.

I'm using Airflow 2.10.3.

Thanks.

[potiuk]

My best advice would be to take a look at the code -there is no indication of namespace parameter being supported, but maybe it's as easy as adding a kwarg parameter to configuration? Or maybe small modification to the underlying code could fix it - then one way you could approach it is to copy the Secrets Backend code (and name it "MyVaultSecretsBackend", configure it to be used in your Airflow instance and modify it so that the namespace is supported.

And then contribute it back so that you can replace it with future backend when new version is released.