[PR] Allow to query config reports

[knoppi]

Description of changes

Enable querying the API endpoint for config reports.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Renaming the host field to host_name on Report is a breaking change for existing callers; consider either supporting both keys or adding a backwards-compatible alias/mapping to avoid runtime failures in existing code.
• Changing the _meta['api_path'] from api/v2/reports to api/v2/config_reports may break any usage that relied on the previous endpoint; if both endpoints must remain usable, consider parameterizing or versioning the path instead of hard-switching it.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Renaming the `host` field to `host_name` on `Report` is a breaking change for existing callers; consider either supporting both keys or adding a backwards-compatible alias/mapping to avoid runtime failures in existing code.
- Changing the `_meta['api_path']` from `api/v2/reports` to `api/v2/config_reports` may break any usage that relied on the previous endpoint; if both endpoints must remain usable, consider parameterizing or versioning the path instead of hard-switching it.

## Individual Comments

### Comment 1
<location path="nailgun/entities.py" line_range="7182-7186" />
<code_context>
     def __init__(self, server_config=None, **kwargs):
         self._fields = {
-            'host': entity_fields.StringField(required=True),
+            'host_name': entity_fields.StringField(required=True),
             'logs': entity_fields.ListField(),
             'reported_at': entity_fields.DateTimeField(required=True),
         }
-        self._meta = {'api_path': 'api/v2/reports'}
+        self._meta = {'api_path': 'api/v2/config_reports'}
         super().__init__(server_config=server_config, **kwargs)

</code_context>
<issue_to_address>
**issue (bug_risk):** Renaming `host` to `host_name` and changing the API path may break existing consumers or deserialization.

Since this class now targets `api/v2/config_reports` and uses `host_name`, verify that:
- The API response actually uses `host_name` (not `host`), and
- No existing code or callers still depend on `Report.host` or the old `api/v2/reports` shape.
If there is existing usage, consider keeping `host` and adding `host_name` as an alias/derived field, or introducing a separate entity for config reports so the original `Report` interface remains unchanged.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Satellite-QE]

Can one of the admins verify this patch?

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[knoppi]

I changed the scope of this PR to adding a new class instead of modifying the class for legacy host reports.

[ogajduse]

LGTM, thank you!

[ogajduse]

Waiting for second review. Is this something @SatelliteQE/team-endeavour wants to take a look at?