What can be configured in a .hcl and what can't?

[jlixfeld]

I’m trying to build a template to automate the configuring of Vault Docker containers, and I’m trying to get a handle on what can be configured through a .hcl file and what cannot.

storage, listener, api, cluster addresses and ui enabling is what makes up my .hcl at the moment, but I would like to do other things like enable secrets engines, auth engines, policies, and roles, among other things.

None of those other things are mentioned at Server Configuration | Vault | HashiCorp Developer so I assume the only way to provision that is to do so via API?

[maxb]

@jlixfeld

I’m trying to get a handle on what can be configured through a .hcl file and what cannot.

HCL is a general syntax used for many purposes. From context, you mean “a Vault server configuration file”. It is important to be specific about that, so you get the right answers.

@jlixfeld

None of those other things are mentioned at Server Configuration | Vault | HashiCorp Developer so I assume the only way to provision that is to do so via API?

Yes.