aws-chaos-engineering-framework 2.0.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (35) hide show
  1. aws_chaos_engineering_framework-2.0.3/.github/release-notes/v2.0.2.md +37 -0
  2. aws_chaos_engineering_framework-2.0.3/.github/release-notes/v2.0.3.md +42 -0
  3. aws_chaos_engineering_framework-2.0.3/.github/workflows/release.yml +238 -0
  4. aws_chaos_engineering_framework-2.0.3/.markdownlint-cli2.yaml +10 -0
  5. aws_chaos_engineering_framework-2.0.3/CHANGELOG.md +73 -0
  6. aws_chaos_engineering_framework-2.0.3/CODE_OF_CONDUCT.md +28 -0
  7. aws_chaos_engineering_framework-2.0.3/CONTRIBUTING.md +53 -0
  8. aws_chaos_engineering_framework-2.0.3/LICENSE +201 -0
  9. aws_chaos_engineering_framework-2.0.3/MANIFEST.in +17 -0
  10. aws_chaos_engineering_framework-2.0.3/PKG-INFO +245 -0
  11. aws_chaos_engineering_framework-2.0.3/README.md +214 -0
  12. aws_chaos_engineering_framework-2.0.3/RELEASING.md +60 -0
  13. aws_chaos_engineering_framework-2.0.3/SECURITY.md +37 -0
  14. aws_chaos_engineering_framework-2.0.3/TESTING.md +54 -0
  15. aws_chaos_engineering_framework-2.0.3/aws_chaos_engineering_framework.egg-info/PKG-INFO +245 -0
  16. aws_chaos_engineering_framework-2.0.3/aws_chaos_engineering_framework.egg-info/SOURCES.txt +33 -0
  17. aws_chaos_engineering_framework-2.0.3/aws_chaos_engineering_framework.egg-info/dependency_links.txt +1 -0
  18. aws_chaos_engineering_framework-2.0.3/aws_chaos_engineering_framework.egg-info/entry_points.txt +2 -0
  19. aws_chaos_engineering_framework-2.0.3/aws_chaos_engineering_framework.egg-info/requires.txt +3 -0
  20. aws_chaos_engineering_framework-2.0.3/aws_chaos_engineering_framework.egg-info/top_level.txt +1 -0
  21. aws_chaos_engineering_framework-2.0.3/aws_chaos_framework.py +8818 -0
  22. aws_chaos_engineering_framework-2.0.3/example-config.yaml +59 -0
  23. aws_chaos_engineering_framework-2.0.3/pyproject.toml +59 -0
  24. aws_chaos_engineering_framework-2.0.3/requirements-build.txt +4 -0
  25. aws_chaos_engineering_framework-2.0.3/requirements-dev.txt +6 -0
  26. aws_chaos_engineering_framework-2.0.3/requirements.txt +3 -0
  27. aws_chaos_engineering_framework-2.0.3/scripts/normalize_sdist.py +203 -0
  28. aws_chaos_engineering_framework-2.0.3/scripts/normalize_wheel.py +275 -0
  29. aws_chaos_engineering_framework-2.0.3/scripts/prepare_release.py +651 -0
  30. aws_chaos_engineering_framework-2.0.3/scripts/verify_distribution.py +187 -0
  31. aws_chaos_engineering_framework-2.0.3/setup.cfg +4 -0
  32. aws_chaos_engineering_framework-2.0.3/tests/test_aws_chaos_framework.py +1660 -0
  33. aws_chaos_engineering_framework-2.0.3/tests/test_normalize_sdist.py +147 -0
  34. aws_chaos_engineering_framework-2.0.3/tests/test_normalize_wheel.py +149 -0
  35. aws_chaos_engineering_framework-2.0.3/tests/test_release_assets.py +177 -0
@@ -0,0 +1,37 @@
1
+ # AWS Chaos Engineering Framework 2.0.2
2
+
3
+ Version 2.0.2 is a distribution and release-integrity update. It does not broaden live AWS behavior or weaken any safety gate from 2.0.1.
4
+
5
+ ## Distribution integrity
6
+
7
+ - Adds an exact standalone Python file, normalized pure-Python wheel, normalized source distribution, SPDX 2.3 dependency SBOM, SHA-256 checksums, and machine-readable release evidence.
8
+ - Requires two independent builds to produce the same six files byte for byte.
9
+ - Pins direct runtime, development, and build inputs for auditable candidate construction.
10
+ - Declares Botocore directly because the framework imports Botocore APIs directly.
11
+ - Creates only a draft GitHub release from a tag that points to a verified protected-main commit.
12
+ - Does not publish to PyPI or any other package registry.
13
+
14
+ ## Validation
15
+
16
+ - Offline framework regressions across Python 3.10 through 3.14.
17
+ - Python 3.12 platform checks on Windows and macOS.
18
+ - Deterministic package normalization, archive safety, exact source identity, wheel metadata, and wheel RECORD checks.
19
+ - Isolated wheel and source-distribution installation checks.
20
+ - Ruff, Bandit, dependency audits, CodeQL, Semgrep, Trivy, dependency review, and full-history Gitleaks.
21
+
22
+ ## Safety boundary
23
+
24
+ Plan mode remains the default. Live execution still requires explicit CLI intent, exact account and region binding, target controls, alarms, and confirmation tokens. Irreversible behavior still requires independent configuration and CLI approval.
25
+
26
+ The release gate never uses AWS credentials and never contacts an AWS account. Use this software only in isolated, non-production environments that you own or are explicitly authorized to test.
27
+
28
+ ## Assets
29
+
30
+ - `AWS-Chaos-Engineering-Framework-v2.0.2.py`: exact standalone runtime
31
+ - `aws_chaos_engineering_framework-2.0.2-py3-none-any.whl`: Python wheel
32
+ - `aws_chaos_engineering_framework-2.0.2.tar.gz`: normalized source distribution
33
+ - `AWS-Chaos-Engineering-Framework-v2.0.2.spdx.json`: SPDX 2.3 direct-dependency SBOM
34
+ - `SHA256SUMS.txt`: SHA-256 digests for the runtime, packages, and SBOM
35
+ - `release-evidence.json`: source commit, artifact identities, dependencies, and archive membership
36
+
37
+ Verify checksums and provenance before installation. Review the plan and every target, alarm, permission, blast-radius, and recovery setting before any authorized live run.
@@ -0,0 +1,42 @@
1
+ # AWS Chaos Engineering Framework 2.0.3
2
+
3
+ Version 2.0.3 is a corrective distribution-only update. It does not broaden live AWS behavior or weaken any safety gate from 2.0.2.
4
+
5
+ ## Why this patch exists
6
+
7
+ Qualification of the unpublished 2.0.2 draft found that its source distribution included the release builder and release tests but omitted the versioned release notes required by those tests. Runtime installation, exact source identity, and the complete 79-entry catalog passed, but the package was not self-testing.
8
+
9
+ The public `v2.0.2` tag remains fixed. Its draft release was not published, and this patch uses a new version rather than moving or reusing that tag.
10
+
11
+ ## Correction
12
+
13
+ - Includes versioned release notes and the tag workflow in the source distribution.
14
+ - Uses a generic release-notes manifest rule so later patch versions inherit the same package contract.
15
+ - Requires repeat builds to contain both release inputs before release assets are accepted.
16
+ - Canonicalizes regular source-archive member modes across mounted Windows filesystems and native Git checkouts.
17
+ - Runs all 101 tests plus 4 parameterized subtests from both the source tree and an extracted source distribution.
18
+
19
+ ## Distribution integrity
20
+
21
+ - Provides an exact standalone Python file, normalized pure-Python wheel, normalized source distribution, SPDX 2.3 dependency SBOM, SHA-256 checksums, and machine-readable release evidence.
22
+ - Requires two independent builds to produce the same six files byte for byte.
23
+ - Pins direct runtime, development, and build inputs for auditable candidate construction.
24
+ - Creates only a draft GitHub release from a tag that points to a verified protected-main commit.
25
+ - Does not publish to PyPI or any other package registry.
26
+
27
+ ## Safety boundary
28
+
29
+ Plan mode remains the default. Live execution still requires explicit CLI intent, exact account and region binding, target controls, alarms, and confirmation tokens. Irreversible behavior still requires independent configuration and CLI approval.
30
+
31
+ The release gate never uses AWS credentials and never contacts an AWS account. Use this software only in isolated, non-production environments that you own or are explicitly authorized to test.
32
+
33
+ ## Assets
34
+
35
+ - `AWS-Chaos-Engineering-Framework-v2.0.3.py`: exact standalone runtime
36
+ - `aws_chaos_engineering_framework-2.0.3-py3-none-any.whl`: Python wheel
37
+ - `aws_chaos_engineering_framework-2.0.3.tar.gz`: normalized source distribution
38
+ - `AWS-Chaos-Engineering-Framework-v2.0.3.spdx.json`: SPDX 2.3 direct-dependency SBOM
39
+ - `SHA256SUMS.txt`: SHA-256 digests for the runtime, packages, and SBOM
40
+ - `release-evidence.json`: source commit, artifact identities, dependencies, and archive membership
41
+
42
+ Verify checksums and provenance before installation. Review the plan and every target, alarm, permission, blast-radius, and recovery setting before any authorized live run.
@@ -0,0 +1,238 @@
1
+ name: Release
2
+
3
+ on:
4
+ push:
5
+ tags:
6
+ - "v*.*.*"
7
+
8
+ permissions:
9
+ contents: read
10
+
11
+ concurrency:
12
+ group: release-${{ github.ref }}
13
+ cancel-in-progress: false
14
+
15
+ jobs:
16
+ build:
17
+ name: Build and verify release assets
18
+ runs-on: ubuntu-latest
19
+ timeout-minutes: 30
20
+ permissions:
21
+ contents: read
22
+ outputs:
23
+ commit: ${{ steps.identity.outputs.commit }}
24
+ version: ${{ steps.identity.outputs.version }}
25
+ steps:
26
+ - name: Check out tagged source
27
+ uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
28
+ with:
29
+ fetch-depth: 0
30
+ persist-credentials: false
31
+
32
+ - name: Set up Python
33
+ uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
34
+ with:
35
+ python-version: "3.12"
36
+ cache: pip
37
+ cache-dependency-path: |
38
+ requirements.txt
39
+ requirements-build.txt
40
+
41
+ - name: Resolve and validate release identity
42
+ id: identity
43
+ shell: bash
44
+ env:
45
+ GH_TOKEN: ${{ github.token }}
46
+ run: |
47
+ set -euo pipefail
48
+ version="${GITHUB_REF_NAME#v}"
49
+ if ! [[ "$version" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
50
+ echo "Tag must contain a stable semantic version" >&2
51
+ exit 1
52
+ fi
53
+ release_commit="$(git rev-list --max-count=1 "$GITHUB_REF_NAME")"
54
+ test "$release_commit" = "$GITHUB_SHA"
55
+ git fetch --no-tags origin main
56
+ git merge-base --is-ancestor "$release_commit" origin/main
57
+ verified="$(gh api "repos/$GITHUB_REPOSITORY/commits/$release_commit" --jq '.commit.verification.verified')"
58
+ test "$verified" = "true"
59
+ test -f ".github/release-notes/$GITHUB_REF_NAME.md"
60
+ if gh release view "$GITHUB_REF_NAME" --repo "$GITHUB_REPOSITORY" >/dev/null 2>&1; then
61
+ echo "A release already exists for $GITHUB_REF_NAME" >&2
62
+ exit 1
63
+ fi
64
+ echo "version=$version" >> "$GITHUB_OUTPUT"
65
+ echo "commit=$release_commit" >> "$GITHUB_OUTPUT"
66
+ echo "epoch=$(git show -s --format=%ct "$release_commit")" >> "$GITHUB_OUTPUT"
67
+
68
+ - name: Install pinned build tools and runtime dependencies
69
+ run: |
70
+ python -m pip install --disable-pip-version-check -r requirements-build.txt
71
+ python -m pip install --disable-pip-version-check -r requirements.txt
72
+
73
+ - name: Build exact release assets
74
+ env:
75
+ RELEASE_COMMIT: ${{ steps.identity.outputs.commit }}
76
+ RELEASE_VERSION: ${{ steps.identity.outputs.version }}
77
+ SOURCE_DATE_EPOCH: ${{ steps.identity.outputs.epoch }}
78
+ shell: bash
79
+ run: |
80
+ set -euo pipefail
81
+ python -m build --no-isolation --wheel --sdist --outdir package-dist
82
+ python scripts/normalize_wheel.py \
83
+ --source-date-epoch "$SOURCE_DATE_EPOCH" \
84
+ package-dist/*.whl
85
+ python scripts/normalize_sdist.py \
86
+ --source-date-epoch "$SOURCE_DATE_EPOCH" \
87
+ package-dist/*.tar.gz
88
+ python -m twine check package-dist/*
89
+ python scripts/verify_distribution.py package-dist
90
+ python scripts/prepare_release.py \
91
+ --version "$RELEASE_VERSION" \
92
+ --tag "$GITHUB_REF_NAME" \
93
+ --source-commit "$RELEASE_COMMIT" \
94
+ --source-date-epoch "$SOURCE_DATE_EPOCH" \
95
+ --dist-directory package-dist \
96
+ --output-directory release-assets
97
+ test "$(find release-assets -maxdepth 1 -type f | wc -l)" -eq 6
98
+
99
+ - name: Rebuild and compare every release byte
100
+ env:
101
+ RELEASE_COMMIT: ${{ steps.identity.outputs.commit }}
102
+ RELEASE_VERSION: ${{ steps.identity.outputs.version }}
103
+ SOURCE_DATE_EPOCH: ${{ steps.identity.outputs.epoch }}
104
+ shell: bash
105
+ run: |
106
+ set -euo pipefail
107
+ python -m build --no-isolation --wheel --sdist --outdir repeat-package-dist
108
+ python scripts/normalize_wheel.py \
109
+ --source-date-epoch "$SOURCE_DATE_EPOCH" \
110
+ repeat-package-dist/*.whl
111
+ python scripts/normalize_sdist.py \
112
+ --source-date-epoch "$SOURCE_DATE_EPOCH" \
113
+ repeat-package-dist/*.tar.gz
114
+ python scripts/prepare_release.py \
115
+ --version "$RELEASE_VERSION" \
116
+ --tag "$GITHUB_REF_NAME" \
117
+ --source-commit "$RELEASE_COMMIT" \
118
+ --source-date-epoch "$SOURCE_DATE_EPOCH" \
119
+ --dist-directory repeat-package-dist \
120
+ --output-directory repeat-release-assets
121
+ test "$(find release-assets -maxdepth 1 -type f -printf '%f\n' | sort)" = \
122
+ "$(find repeat-release-assets -maxdepth 1 -type f -printf '%f\n' | sort)"
123
+ for artifact in release-assets/*; do
124
+ cmp --silent "$artifact" "repeat-release-assets/${artifact##*/}"
125
+ done
126
+
127
+ - name: Exercise the exact standalone asset
128
+ env:
129
+ AWS_EC2_METADATA_DISABLED: "true"
130
+ RELEASE_VERSION: ${{ steps.identity.outputs.version }}
131
+ shell: bash
132
+ run: |
133
+ set -euo pipefail
134
+ version_output="$(python "release-assets/AWS-Chaos-Engineering-Framework-v$RELEASE_VERSION.py" --version)"
135
+ test "$version_output" = "AWS Chaos Engineering Framework $RELEASE_VERSION"
136
+ python "release-assets/AWS-Chaos-Engineering-Framework-v$RELEASE_VERSION.py" --help >/dev/null
137
+ python "release-assets/AWS-Chaos-Engineering-Framework-v$RELEASE_VERSION.py" --list-experiments >/dev/null
138
+
139
+ - name: Preserve the exact release assets
140
+ uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
141
+ with:
142
+ name: release-assets
143
+ path: release-assets/
144
+ if-no-files-found: error
145
+ retention-days: 14
146
+
147
+ attest:
148
+ name: Attest release assets
149
+ needs: build
150
+ runs-on: ubuntu-latest
151
+ timeout-minutes: 10
152
+ permissions:
153
+ contents: read
154
+ id-token: write
155
+ attestations: write
156
+ steps:
157
+ - name: Download the exact release assets
158
+ uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
159
+ with:
160
+ name: release-assets
161
+ path: release-assets
162
+
163
+ - name: Attest every release asset
164
+ uses: actions/attest-build-provenance@4d101475d8b20a2381f78447822ac1eab6504dd8 # v4.2.2
165
+ with:
166
+ subject-path: release-assets/*
167
+
168
+ draft:
169
+ name: Create and verify draft release
170
+ needs: [build, attest]
171
+ runs-on: ubuntu-latest
172
+ timeout-minutes: 10
173
+ permissions:
174
+ contents: write
175
+ steps:
176
+ - name: Check out tagged release notes
177
+ uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
178
+ with:
179
+ persist-credentials: false
180
+
181
+ - name: Download the exact release assets
182
+ uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
183
+ with:
184
+ name: release-assets
185
+ path: release-assets
186
+
187
+ - name: Create draft release
188
+ env:
189
+ GH_TOKEN: ${{ github.token }}
190
+ RELEASE_COMMIT: ${{ needs.build.outputs.commit }}
191
+ RELEASE_VERSION: ${{ needs.build.outputs.version }}
192
+ shell: bash
193
+ run: |
194
+ set -euo pipefail
195
+ gh release create "$GITHUB_REF_NAME" \
196
+ --repo "$GITHUB_REPOSITORY" \
197
+ --draft \
198
+ --verify-tag \
199
+ --target "$RELEASE_COMMIT" \
200
+ --title "AWS Chaos Engineering Framework $RELEASE_VERSION" \
201
+ --notes-file ".github/release-notes/$GITHUB_REF_NAME.md" \
202
+ "release-assets/AWS-Chaos-Engineering-Framework-v$RELEASE_VERSION.py" \
203
+ "release-assets/aws_chaos_engineering_framework-$RELEASE_VERSION-py3-none-any.whl" \
204
+ "release-assets/aws_chaos_engineering_framework-$RELEASE_VERSION.tar.gz" \
205
+ "release-assets/AWS-Chaos-Engineering-Framework-v$RELEASE_VERSION.spdx.json" \
206
+ "release-assets/SHA256SUMS.txt" \
207
+ "release-assets/release-evidence.json"
208
+
209
+ - name: Verify exact draft state
210
+ env:
211
+ GH_TOKEN: ${{ github.token }}
212
+ RELEASE_VERSION: ${{ needs.build.outputs.version }}
213
+ shell: bash
214
+ run: |
215
+ set -euo pipefail
216
+ gh release view "$GITHUB_REF_NAME" \
217
+ --repo "$GITHUB_REPOSITORY" \
218
+ --json isDraft,isPrerelease,assets > release-state.json
219
+ python - "$RELEASE_VERSION" <<'PY'
220
+ import json
221
+ import sys
222
+
223
+ version = sys.argv[1]
224
+ state = json.load(open("release-state.json", encoding="utf-8"))
225
+ expected = {
226
+ f"AWS-Chaos-Engineering-Framework-v{version}.py",
227
+ f"aws_chaos_engineering_framework-{version}-py3-none-any.whl",
228
+ f"aws_chaos_engineering_framework-{version}.tar.gz",
229
+ f"AWS-Chaos-Engineering-Framework-v{version}.spdx.json",
230
+ "SHA256SUMS.txt",
231
+ "release-evidence.json",
232
+ }
233
+ actual = {asset["name"] for asset in state["assets"]}
234
+ if state["isDraft"] is not True or state["isPrerelease"] is not False:
235
+ raise SystemExit("Release must remain a non-prerelease draft")
236
+ if actual != expected:
237
+ raise SystemExit(f"Unexpected release asset set: {sorted(actual)}")
238
+ PY
@@ -0,0 +1,10 @@
1
+ config:
2
+ MD013: false
3
+ MD024:
4
+ siblings_only: true
5
+ globs:
6
+ - "**/*.md"
7
+ ignores:
8
+ - ".git/**"
9
+ - ".venv/**"
10
+ - "venv/**"
@@ -0,0 +1,73 @@
1
+ # Changelog
2
+
3
+ All notable changes to this project are documented here.
4
+
5
+ ## 2.0.3 - 2026-08-28
6
+
7
+ ### Fixed
8
+
9
+ - included the active versioned release notes and tag workflow in the source distribution so its bundled release-construction tests pass from an extracted package
10
+ - added an archive-membership regression that verifies both release inputs before any candidate is accepted
11
+ - canonicalized regular source-archive member modes so mounted and native build filesystems produce identical bytes
12
+
13
+ ### Changed
14
+
15
+ - advanced the recovery candidate to 2.0.3 because the existing public `v2.0.2` tag remains fixed and its draft release was not published
16
+ - replaced the hard-coded current-version manifest entry with a generic release-notes rule so later patch versions inherit the same self-test contract
17
+
18
+ ## 2.0.2 - 2026-08-28
19
+
20
+ ### Added
21
+
22
+ - reproducible wheel, source archive, standalone script, SPDX SBOM, checksums, and release evidence
23
+ - tag-only release automation that creates a draft release for human review
24
+ - offline package validation on Linux, Windows, and macOS
25
+
26
+ ### Changed
27
+
28
+ - pinned runtime, development, and build dependencies for auditable release inputs
29
+ - declared Botocore as a direct runtime dependency because the application imports it directly
30
+ - constrained supported Python versions to the tested 3.10 through 3.14 range
31
+
32
+ ### Security
33
+
34
+ - release assembly now rejects unsafe archive paths and validates exact package contents
35
+ - distribution builds are normalized and compared byte for byte before release assets are accepted
36
+
37
+ ## 2.0.1 - 2026-08-12
38
+
39
+ ### Fixed
40
+
41
+ - initialized rollback metadata explicitly for every supported experiment path
42
+ - removed unnecessary test-double variable deletion flagged by CodeQL
43
+ - added a regression test for complete experiment safety metadata
44
+
45
+ ## 2.0.0 - 2026-08-12
46
+
47
+ ### Added
48
+
49
+ - guarded orchestration for existing AWS FIS experiment templates
50
+ - fail-closed account, partition, credential, alarm, target, and blast-radius controls
51
+ - exact live confirmation tokens and dual approval for irreversible actions
52
+ - tag-scoped VPC discovery and exact target allowlisting
53
+ - cooperative emergency stops and runtime safety monitoring
54
+ - mutation-attempt and rollback-attempt evidence
55
+ - atomic, privacy-conscious JSON reports
56
+ - CLI commands for sample configuration, validation, catalog inspection, and token display
57
+ - deterministic offline tests for every advertised executable experiment mode
58
+
59
+ ### Changed
60
+
61
+ - plan mode is now the default and live mode is CLI-only
62
+ - automatic rollback reports failure when recovery cannot be verified
63
+ - resource-policy faults preserve existing policy statements and exempt the active break-glass principal
64
+ - unsupported or non-credible actions are explicitly gated
65
+ - logs redact credentials, ARNs, account IDs, and registered target identifiers
66
+
67
+ ### Fixed
68
+
69
+ - AWS SDK service and request-model errors across AppStream, WAF, VPC routing, and other service extensions
70
+ - fail-open safety checks and missing-alarm handling
71
+ - IAM self-lockout paths involving the active role or access key
72
+ - suite failures that could previously be reported as successful
73
+ - unsafe report overwrite and non-atomic report output
@@ -0,0 +1,28 @@
1
+ # Code of Conduct
2
+
3
+ ## Our commitment
4
+
5
+ We are committed to a respectful, harassment-free community for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, experience level, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
6
+
7
+ ## Expected behavior
8
+
9
+ - Be respectful, constructive, and technically honest.
10
+ - Give and accept useful feedback with empathy.
11
+ - Focus disagreement on ideas and evidence, not people.
12
+ - Protect private information and security-sensitive details.
13
+ - Respect project scope, safety controls, and maintainer decisions.
14
+
15
+ ## Unacceptable behavior
16
+
17
+ - harassment, threats, discrimination, or personal attacks
18
+ - sexualized language or unwanted attention
19
+ - trolling, sustained disruption, or deliberate misinformation
20
+ - publishing another person's private information without permission
21
+ - encouraging unauthorized access or unsafe testing
22
+ - conduct that would reasonably be considered inappropriate in a professional setting
23
+
24
+ ## Enforcement
25
+
26
+ Report conduct concerns privately to the project maintainers using the contact method listed on the repository owner's GitHub profile. Maintainers may edit or remove contributions and may temporarily or permanently restrict participation when behavior violates this policy.
27
+
28
+ Reports will be reviewed fairly and with appropriate confidentiality. Retaliation against a reporter is not permitted.
@@ -0,0 +1,53 @@
1
+ # Contributing
2
+
3
+ Thank you for helping improve the AWS Chaos Engineering Framework.
4
+
5
+ ## Ground rules
6
+
7
+ - Keep the runtime application in the single `aws_chaos_framework.py` file.
8
+ - Keep plan mode free of mutating AWS calls.
9
+ - Prefer AWS FIS when it supplies a managed fault.
10
+ - Fail closed when identity, target scope, alarms, or recovery state is uncertain.
11
+ - Never add credentials, account IDs, ARNs, internal resource names, or generated reports.
12
+ - Do not test a pull request against an AWS account as part of the public test suite.
13
+ - Use ASCII punctuation and do not introduce em dashes.
14
+
15
+ ## Development setup
16
+
17
+ ```powershell
18
+ python -m venv .venv
19
+ .\.venv\Scripts\Activate.ps1
20
+ python -m pip install --upgrade pip
21
+ python -m pip install -r requirements-dev.txt
22
+ ```
23
+
24
+ Run the release checks:
25
+
26
+ ```powershell
27
+ python -m ruff format --check .
28
+ python -m ruff check .
29
+ python -m pytest -q
30
+ python -m bandit -q -r .\aws_chaos_framework.py
31
+ python -m pip_audit -r .\requirements.txt
32
+ ```
33
+
34
+ ## Adding or changing an experiment
35
+
36
+ Every executable experiment must provide:
37
+
38
+ 1. explicit support and risk metadata
39
+ 2. strict configuration validation
40
+ 3. bounded target selection
41
+ 4. a read-only plan path
42
+ 5. mutation-attempt tracking
43
+ 6. an honest rollback classification
44
+ 7. deterministic offline tests for success and failure paths
45
+ 8. Botocore-model-valid operation and request names
46
+
47
+ If exact recovery cannot be implemented, classify the action as irreversible or unsupported. Do not label best-effort recreation as automatic rollback.
48
+
49
+ ## Pull requests
50
+
51
+ Keep pull requests focused. Explain the safety impact, test coverage, configuration changes, and documentation changes. New behavior should include tests that fail before the fix and pass after it.
52
+
53
+ All contributions are licensed under the Apache License 2.0.