Add GIS telematics import and access-point report modules

[vansh-deepsource]

No description provided.

[deepsource-development]

DeepSource Code Review

We reviewed changes in 9d1323c...f503b1f on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Focus Area: Reliability

Security   Reliability   Complexity   Hygiene

Feedback

Boundary handling around external data

• The three issues line up around edges of external input: escaping tab/newline in exported fields, coercing config booleans from settings[key], and assuming attributes is always a dict for .items().
• You’re already encapsulating payload/config nicely; tightening the “what shape do we accept at the boundary?” story would catch these together.

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Ansible		Jun 9, 2026 8:27a.m.	Review ↗
Helm		Jun 9, 2026 8:27a.m.	Review ↗
Python		Jun 9, 2026 8:27a.m.	Review ↗
Secrets		Jun 9, 2026 8:27a.m.	Review ↗

[deepsource-development]

Unescaped `\t`/`\n` fields enable protocol record injection

Payload fields are inserted directly into a tab/newline-delimited protocol. If upstream data contains \n or \t, attackers can split lines and inject unintended records, corrupting import integrity.
Add strict escaping or validation for every serialized field before concatenation, rejecting control characters in check_import_table_data and build_header

[deepsource-development]

`row.get("attributes", {})` can be `None`, causing `.items()` crash

rows may include malformed records where attributes is None or another non-dict type. Iteration then raises AttributeError, failing the whole import batch.
Add a mapping type check and fallback to {} or skip invalid rows with explicit validation before .items()

[deepsource-development]

`settings[key]` boolean coercion corrupts non-boolean import settings

override_import_settings normalizes every allowed key as boolean. Non-boolean configuration entries can be silently converted to 0/1, which can produce invalid import settings and rejected downstream imports.

Restrict boolean normalization to explicit boolean keys and preserve sanitized string overrides for non-boolean keys.