sensu_secret 'prod_foo' do
id '/secrets/prod/foo'
namespace 'prod'
secrets_provider 'vault'
end
sensu_secret 'test_foo' do
id '/secrets/test/foo'
namespace 'test'
secrets_provider 'vault'
end
Output
This creates a secret called prod_foo in the namespace prod and test_foo in the namespace test.
Impact
This creates a more complicated environment where every asset in Sensu has to be aware of its own namespace.
Expected Behavior
It would be better if they could both be called foo. However, that is impossible because every resource in Chef must have a unique name and that name is used as the name of the resource in Sensu.
sensu_secret 'prod_foo' do
id '/secrets/prod/foo'
namespace 'prod'
secrets_provider 'vault'
secret_name 'foo'
end
sensu_secret 'test_foo' do
id '/secrets/prod/foo'
namespace 'prod'
secrets_provider 'vault'
secret_name 'foo'
end
Chef Version
Input
Output
This creates a secret called
prod_foo
in the namespaceprod
andtest_foo
in the namespacetest
.Impact
This creates a more complicated environment where every asset in Sensu has to be aware of its own namespace.
Expected Behavior
It would be better if they could both be called
foo
. However, that is impossible because every resource in Chef must have a unique name and that name is used as the name of the resource in Sensu.Actual Behavior
As described above.
Steps to Reproduce your problem
As described above.