[icinga] Role creates password for icinga_web
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
The debops.icinga role can currently create the password of the Icinga Director API user, using the 'password' lookup. See icinga__director_register_api_password. The password must however be managed by the debops.icinga_web role because it needs to configure the API credentials. Both roles having "write access" to the Icinga Director password has proven confusing (ask @stefangweichinger).
I propose that we only let the debops.icinga_web role create the password, so that debops.icinga can show a more helpful error if it does not exist.
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 tracing the icinga__director_register_api_password variable in the debops.icing role and inspect how debops.icing_web configures the Icinga Director API credentials. Confirm where each role currently creates or consumes the password, then verify that icinga_web owns creation and icinga reports a helpful error when the password is absent.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100