theforeman / theforeman/puppet-puppet
Support `server_list` for agent config
Nobody has claimed this yet.
- Dominant language
- Puppet
- Stars
- 97
- Forks
- 243
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 1
Description
For my remote data centers, I've got a puppet server co-located out there. But sometimes it is down for maintenance.
Rather than setting up fancy DNS, I'd prefer to just add the local puppet to the front of my server_list where needed.
I'm not sure if this should or shouldn't be exclusive with the single server. Perhaps puppet::agent_server_hostname should become either a String or Array[String[1]] and switch between them as needed?
I don't have a great feeling for what the overall interface should feel like...
https://help.puppet.com/core//current/Content/PuppetCore/Markdown/configuration.htm#server_list
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the agent configuration interface around puppet::agent_server_hostname and read the linked Puppet server_list documentation. Clarify whether server and server_list are mutually exclusive and how an array should be represented in this module. Done means the supported interface and its expected behavior are documented and covered by the module's relevant checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100