Skip to content
New issue

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

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

Already on GitHub? # to your account

Enterprise data bag for enterprise repo credentials does not seem to work #595

Open
jshrack-ssi opened this issue Dec 17, 2017 · 3 comments

Comments

@jshrack-ssi
Copy link

jshrack-ssi commented Dec 17, 2017

Expected Behavior

Sensu Enterprise yum repo url is populated with credentials from data bag as defined by enterprise_item attribute.

Current Behavior

Even with the sensu data bag and enterprise_item data bag item configured the credentials are not set for the enterprise repo which causes a repo failure.

Steps to Reproduce (for bugs)

  1. Set sensu data bag name attribute to: default["sensu"]["data_bag"]["name"] = "sensu"
  2. Set sensu enterprise item to: default["sensu"]["data_bag"]["enterprise_item"] = "enterprise"
  3. Configure enterprise item contents to the following:
{
  "id": "enterprise",
     "repository": {
        "credentials": {
           "user": "user",
           "password": "password"
        }
     }
}
  1. Run chef client.

Context

Your Environment

  • Version of this cookbook used: 4.1.0
  • Version of Sensu used: Sensu: 1.1.2, Sensu Enterprise: 2.7.0-1
  • Version of Chef used: 12.18.31
  • Operating System and version (e.g. CentOS 7, Ubuntu 14.04): CentOS 7
@jshrack-ssi
Copy link
Author

I figured it out. The enterprise item does not seem to support encrypted data bags. Perhaps this would be a good idea given the content?

@majormoses
Copy link
Contributor

I don't have enterprise to test with I'd accept a pull request for it though.

@majormoses
Copy link
Contributor

If there is need I can probably throw together a PR if someone can test it for me.

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

No branches or pull requests

2 participants