theforeman / theforeman/foremanctl
Changing hostname should be trivial
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27
- Forks
- 47
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 40
Description
The current installer and deployment design rely heavily on hostname, and require a lot of work, including touching of APIs to change data models inside Foreman whenever it changes. A goal of the container deployment and new installer should be to make changing hostname both inherent and as trivial as possible.
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 by reviewing the installer and container deployment design, then trace where hostname is used in Foreman APIs and data models. The issue provides no specific files or tests; done means changing the hostname requires minimal work without modifying Foreman data models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100