cyberark / conjur-puppet

Official Puppet module for CyberArk Conjur
https://forge.puppet.com/cyberark/conjur
Apache License 2.0
6 stars 3 forks source link

Puppet module has undergone XA #123

Closed izgeri closed 3 years ago

izgeri commented 4 years ago

Document any issues you encounter in trying to figure out how to use this module, and troubleshooting UX as issues are encountered.

diverdane commented 4 years ago

Test Setup

Intent is to use Linux VMs to make it as "production-like" as possible, and to test with a different Puppet master/agent than the containers we use in local/integrations.

Puppet Master/Agent VMs are connected via a private (host-only) VirtualBox network, with fixed IPs and /etc/hosts entries added to allow agent to connect to master and vice versa.

Tests

Any other suggestions???

Findings (So Far)

  1. Forge doc has broken link for REFERENCE.md here: https://forge.puppet.com/cyberark/conjur#reference
  2. Forge doc has broken link for metadata.json here: https://forge.puppet.com/cyberark/conjur#limitations
  3. (Tiny nit, should have caught this earlier) In the [Conjur Module Basics](https://github.com/cyberark/conjur-puppet#conjur-module-basics] section of the main README.md
    • "agent-side" identity can probably be "pre-provisioned" to match desriptions below.
    • "server-provided configuration" can probably be "Puppet manifest based" or something like that to match what's below.
  4. Might help to have some troubleshooting hints:
    • Use '--trace' and '--verbose' when running puppet agent to get verbose output with traces, e.g. `sudo /opt/puppetlabs/bin/puppet agent --trace --verbose --test'
    • Use 'systemctl status puppetserver' to check server status on a Linux host
    • Use 'journalctl -xe' to get puppetserver logs on a Linux host
izgeri commented 3 years ago

@sgnn7 I am going to close this to close out M3, but can you please make sure any follow-up cards have been filed and placed in M4 as appropriate? Thank you!!