Skip to content

feat(prowler): chunk11 add the AWS service routes (#422) - #441

Draft
Christophe Melchior (Kakudou) wants to merge 4 commits into
feat/422-prowler-injector-chk10-base-kubernetesfrom
feat/422-prowler-injector-chk11-service-aws
Draft

feat(prowler): chunk11 add the AWS service routes (#422)#441
Christophe Melchior (Kakudou) wants to merge 4 commits into
feat/422-prowler-injector-chk10-base-kubernetesfrom
feat/422-prowler-injector-chk11-service-aws

Conversation

@Kakudou

Copy link
Copy Markdown
Member

Part of #422.

Chunk 11 of the Prowler injector stack: add the AWS service routes — the CHK.011 AWS service assessment: the BDD suite (behaviour, OCSF status / lifecycle logs / verbose diagnostics / OCSF capture fixtures), the three AWS service routes (IAM, S3, EC2) in contracts/aws.py with shared AWS finding selection, their registration in the registry / __init__ (the first service-level executable contracts after the four provider bases), and the final OCSF capture alignment — including the cross-chunk BDD updates (chk001, chk007, chk008, chk009, chk010) and the chk006 unit registry expectations.

Re-landed from feat/422-prowler-chk011-service-aws-assessment (13b112f..5379174): 12 source commits folded into 4 (J1: 3d0adbb; J2: 223a897 + 6b96cc9; J3: 702c151 + e0a50f7; J4: 28236c4 + 33bd00d + ff86f9d + 477608a + 253204e + 5379174). J2 and J3 landed at the source-final post-images, so the later alignment content was already in place and J4 was a single no-conflict cherry-pick of 28236c4 (auto-merged the registry test to the final state; left the CHK.011 BDD a no-op). Gate V (whole-branch tree vs source tip 5379174): byte-identical except (a) the 14 pyproject.toml version differences of the other injectors (base move to 3.260821.0; prowler/ untouched), (b) the 8 trap-analysis.md files (chk004–chk011) excluded by standing call, and (c) one approved deviation — the pinned pyoaev version assert removed from prowler/tests/unit/chk006_executable_base/test_outputs_registry_runtime.py.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants