MISSED DEPLOYMENT ERROR
Help cover an error without sharing the whole log
If SAM Doctor says no supported pattern matched, a small, reviewed excerpt is enough to investigate a new rule. Never paste a complete production log, credentials, account IDs, ARNs, tokens, customer data, or private repository names into a public issue.
1. CAPTURE
Create a short request packet locally
Run the command against the log that produced no finding. It writes a 5–15 line window around the first likely error, with the same common redactions SAM Doctor uses in reports.
sam-doctor request-packet deployment.log --output-dir artifactsThis is a starting point, not a guarantee that every sensitive value was removed. The source log stays local; only the generated excerpt is intended for review.
2. REVIEW
Keep only the evidence needed to understand the failure
- Keep the first error and a few lines of surrounding context.
- Remove account IDs, ARNs, hostnames, customer data, repository names, credentials, and tokens.
- Record the deployment command and the AWS or CI service involved.
- If you do not know the right next check, say so; that uncertainty is useful context.
3. SUBMIT
Open a focused rule request
Paste the reviewed excerpt into the rule-request form. The form asks
for the service, the command that failed, and the safest next check to
investigate. If you are unsure about the last one, write: Not
sure — please suggest the safest first check.
Open a diagnostic rule request or check the exact-error index first in case the failure already has a guide.