Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide sensitive data values #45

Closed
linuxmail opened this issue May 5, 2017 · 4 comments
Closed

Hide sensitive data values #45

linuxmail opened this issue May 5, 2017 · 4 comments

Comments

@linuxmail
Copy link

linuxmail commented May 5, 2017

Hello,

  • Puppet: node: 3.7.2-4 / puppet server: 2.7.2-1puppetlabs1 / puppetdb: 4.4.0-1puppetlabs1
  • Distribution: Debian Jessie
  • Module version: latest

How to reproduce (e.g Puppet code you use)

class profile::grafana::base (
...
  $grafana_database_password = Sensitive(hiera('monitoring::grafana::database::password')),
...
)
{
...
  $database_cfg = {
    database => {
      type     => 'mysql',
      host     => "${database_server}:3306",
      name     => "$grafana_database",
      user     => "$grafana_database_user",
      password => $grafana_database_password.unwrap,
    }
  }
....

What are you seeing

Password in plaintext

I trying to hide all secrets from logs and the PuppetDB server. The secrets are saved in hiera-eyaml, but I can't find a way to hide the secrets for database/ldap.

Is there a way to support it?

cu denny

@wyardley
Copy link

I agree that this is a problem, not sure what the fix would be since as of now, the config hash is just a straight passthrough.

@alexjfisher
Copy link
Member

Is this the same issue as #82 or just related?

@dhoppe
Copy link
Member

dhoppe commented Mar 26, 2019

@alexjfisher I am not sure if this is related, because the Puppet type Sensitive has been introduced with Puppet 4.6, but he uses Puppet 3.7.

@linuxmail
Copy link
Author

hi,

we switched to Puppet5 and we have the same problem on many Puppet modules too, so I close the issue, until there is a reliable way to solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants