Vault is loading config files in the opposite order described in the documentation

[fernando-villalba]

Following this advice I created a file called storage.hcl in the config folder for vault with the following configuration:

storage "consul" {
  address = "127.0.0.1:8501"
  path    = "vault/"
  scheme  = "https"
  service = "vault"
}

However this configuration block in the default.hcl was not overruled.

I changed the name of the file to astorage.hcl and now the configuration in default.hcl is overruled. This is bizarre because in the consul cluster it works exactly as you described but here it works the other way around.

I am using vault v1.3.2

It gets weirder.

After changing the order of the files, restarting and it working, I renamed the file astorage.hcl to storage.hcl again and restarted and it works.

Then I renamed the file to blah.blah and restarted and it didn't work as expected (just to see if there was anything cached somewhere).

But when I renamed the file back to storage.hcl it worked, and trying yet again to astorage.hcl also worked....

Really confused by this and not sure if it's a very predictable method of overriding configuration.