feat: add workloads command#18
Merged
TacoRocket merged 2 commits intomainfrom Apr 1, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a new
workloadscommand that builds a joined workload census across VMs, VMSS, App Service, and Function workloads using existing identity and endpoint data.This also wires the command through the CLI, registry, help surface, table and CSV output, schema snapshot, golden output, and test coverage.
Why this changed
Phase 3 calls for a workload-focused operator view after the network foundation slices. The goal is to show which workloads exist, what identity context they carry, and which reachable endpoints are already visible without expanding into deeper service-specific or effective-network analysis.
Impact
Operators now get a single workload census view that joins compute and web workloads with visible ingress and managed identity context.
As process-driven carry-forward for a clean publish path, this branch also includes the already-agreed Key Vault omitted-ACL fixture and finding updates that were present in the local dirty main worktree.
Validation
python3 -m ruff check src tests scriptsPYTHONPATH=src python3 -m pytest tests/test_collectors.py tests/test_golden_outputs.py tests/test_contract_schemas.py tests/test_cli_smoke.py tests/test_help.py tests/test_terminal_ux.py tests/test_models.pyNo implementation-vs-plan drift found.