Move host facts count health check to the Foreman API
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
Research direction
Start at check_host_facts_count and the existing /api/v2/fact_values path, then read the OAuth authentication pathway and task/permission query migrations named in the issue. Done means the check uses a supported per-host fact-count API, no longer needs Foreman database credentials, preserves threshold and all-host reporting, and has integration coverage.
Written by the indexing model from the issue text.
Description
check_host_facts_count is the remaining post-deployment health check that reads Foreman application data directly from PostgreSQL.
The current /api/v2/fact_values endpoint returns complete fact values. Using it for this check would transfer every fact from every host and does not provide an efficient per-host aggregate, so replacing the single grouped SQL query with it would regress large deployments.
Once Foreman exposes a supported per-host fact count through the API:
- switch
check_host_facts_countto OAuth-authenticated API access - remove its dependency on Foreman database credentials
- retain the current threshold and all-host reporting behavior
- add integration coverage for the API path
Split from #551 so the existing OAuth authentication pathway and the task/permission query migrations can land independently.
- Dominant language
- Python
- Stars
- 26
- Forks
- 56
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from theforeman/foremanctl
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
theforeman/foremanctl#982 · 1 comment ·
Maintainers usually reply within 1 day
-
Stop checking the removed Katello event daemonPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
theforeman/foremanctl#913 ·
Maintainers usually reply within 1 day
-
Wait for Foreman tasks in backup integration testsPossibly taken @jakduch claimed this 45 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
theforeman/foremanctl#894 ·
Maintainers usually reply within 1 day
-
Serialize image service pullsPossibly taken @jakduch claimed this 45 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
theforeman/foremanctl#881 ·
Maintainers usually reply within 1 day
-
Use a larger fapolicyd subject cache in deployment testsPossibly taken @jakduch claimed this 45 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
theforeman/foremanctl#880 ·
Maintainers usually reply within 1 day
All issues in theforeman/foremanctl
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
SACGF/variantgrid#2791 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bot-triaged oncall: cpu inductor
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kubescape/cel-admission-library#141 · 1 comment ·
Maintainers usually reply within 1 day