ENT-1544 B1: GStreamer RTSPS with CA bundle and TLS validation flags

[NVergunst-ROBO]

Summary

• Add shared rtsp_tls helpers (ROBOFLOW_RTSP_TLS_VALIDATION_FLAGS → GStreamer tls-validation-flags suffix).
• Scaffold for Jetson rtspsrc pipeline wiring (reference: agent/fix-jetson-nvjpeg-runtime jetson_producer.py).
• Plan: cursor-cloud/features/ent-1544/plans/B1-inference.md.

ENT-1544

Phase B — primary RTSPS decode path for edge Jetson devices.

Type of change

• New feature (non-breaking change which adds functionality)

How has this change been tested, please provide a testcase or example of how you tested the change?

• test_rtsp_tls.py unit tests for env parsing and rtsps URL detection.

Dependencies

• B3 (rfdm) for fleet env injection; secure default works without B3.

Test plan

• pytest tests/inference/unit_tests/core/interfaces/camera/test_rtsp_tls.py
• Follow-up: Jetson rtspsrc integration + manual RTSPS camera test

Made with Cursor

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Nicholas Vergunst seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

👋 Thanks for the pull request! Here is how automated Claude review works here, so you spend credits (and reviewer time) wisely.

🚧 Right now this is a draft, so automated Claude review is paused — nothing is being spent yet. Mark it Ready for review to trigger it.

Warning

💸 The Claude reviewer bills in credits, not vibes

Automated review spins up a real agent that reads real code and spends real credits on every pass. It is glad to help — but it is not a rubber duck, a linter you poke in a loop, or a substitute for reading the contributing guide. Treat it like an expensive senior reviewer whose time you booked, and show up prepared.

Draft when unsure, Ready when you mean it:

• 🌱 Not sure the PR is in good shape yet? Keep it (or set it back) as a draft — drafts pause review, so you can push and iterate without burning credits on a moving target.
• 💪 Feel strong about the contents? Mark it Ready for review and the reviewer will take a look.

However you get there, arrive prepared:

• 🧱 Bring a SOLID, thorough PR. Point your local agent at our skills/ to tune it to our guidelines first — or, if you are one of those fabled carbon-based contributors, read them yourself. A half-baked diff costs exactly the same to review as a finished one.
• ✅ Resolve every comment before you re-request review. Re-requesting with threads still open means paying twice for the same conversation.
• 🔁 Do not use CI review as an inner loop for a local agent. The reviewer is not a step-by-step debugger — do the unfolding locally and arrive with the answer, not the search.
• 🙋 If something looks off, ask a human. One question to a maintainer is cheaper and faster than three rounds of agent re-review chasing a misread.

Reviews are not free. A draft costs nothing to review; a Ready PR is a promise that it is worth reviewing.

• Prefer to skip automated review entirely? Add the skip-claude-review label.