Repository navigation
improvement(aws-marketplace): close billing gaps and simplify the license write paths - #9946
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 40009848 | Triggered | Generic Password | c48df42 | helm/sim/examples/aws-marketplace-prerequisites.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
[Medium impact] The PR appears safe to merge with the open-checkout race explicitly deferred. SummaryThis PR tightens AWS Marketplace billing checks and combines repeated license writes.
The earlier pending-payment finding is fixed. waleedlatif1 accepted and deferred the open-checkout race: a Stripe checkout already in progress can finish after Marketplace linking. Their stated follow-up is to check Marketplace ownership when the Stripe completion webhook runs. Neither supplied root thread has a comment number, so neither receives a numbered previous-finding entry.
|
6c01fb8 to
26591af
Compare
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
…ense write paths - Refuse linking a Marketplace license to an organization already paying Stripe for a self-serve plan, so it is never billed twice - Count only listings this deployment sells when blocking Stripe checkout - Never add to a usage record after it is frozen for sending, even under a lock taken for another organization - Container license: require a grant the account may use, and stagger replica restarts on a license change - CloudFormation prerequisites: a fixed URL-safe database password instead of RDS's rotating one; placeholder product ID in the example values - One insert path, one claim invariant, and one once-only notice helper in the repository; shared claim lookup, lock recheck, and audit entry in the use cases
…ling the organization - A trialing or incomplete self-serve subscription becomes a charge, so linking refuses any bound subscription that is not finished; an abandoned checkout with no Stripe subscription stays linkable - Example values name the CloudFormation outputs as secret ARNs and mark the product ID as editable
26591af to
8e9c0d4
Compare
|
@cubic-dev-ai review this PR |
|
@GitGuardian The flagged line in helm/sim/examples/aws-marketplace-prerequisites.yaml is a CloudFormation dynamic reference ({{resolve:secretsmanager:...}}) to a password that CloudFormation generates in Secrets Manager at deploy time; no secret value is in the template. False positive. |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
Summary
Type of Change
Testing
lifecycle.integration.ts,metering.integration.ts,checkout-guard.integration.tsagainst Postgres: 96 passauthorization.test.ts,entitlements.test.ts,aws-marketplace.test.tsx: 22 passbun run lint,type-check,check:audits(all but the local-only docs content registry);aws cloudformation validate-templateon the prerequisites templateChecklist
test-auditauthoring gate)