Run tapirx as PID 1 in discovery scenario

[t-a-y-l-o-r]

Summary

• Remove passive-discovery docker exec anti-pattern — tapirx now runs as PID 1 via its entrypoint
• Add enable-waffle-switch command (required by new BlueFlow upsert endpoint)
• Add TAPIRX_UPSERT_URL env var to testbed topology
• Add tapirx.local.Dockerfile for building from local source

Context

The old scenario ran tapirx via docker exec (detached) into an already-running container. This meant PID 1 was a useless tapirx process with no API URL, the real worker's logs were lost, and two processes competed for packets on the same interface.

Dependencies

• Depends on Add configurable HTTP verb and update BlueFlow field names tapirx#23 (entrypoint reads env vars when no CLI args provided)
• Related to feat: modernize upsert endpoint for passive scanners blueflow#78 (upsert endpoint migration)

Test plan

• Integration test 3 passes: post-change tapirx + post-change blueflow → 1 asset created

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9e4b7cb9-8f50-46f8-9042-c89e3fafa09f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/upsert-migration-tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}