CDK: check SCP (service control policies) as you type
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
## Problem
Developers can author CDK code that isn't deployable.
> 1. SCP Intellisense.
> 2. Pull down tests from a Construct hub
>
> We don't want to be in a situation where we write a stack and cannot deploy it because of Company SCPs so intellisense would be for the win here. We also need to have Globally defined Stack tests so that we cannot push code to CodeCommit which won't be able to be deployed even if a dev ignores the intellisense.
>
> We want speed and we want to intercept non-compliant code as the dev types.
_Originally posted by @sholtomaud in https://github.com/aws/aws-toolkit-vscode/issues/751#issuecomment-1137006198_
## Solution
Can AWS Toolkit check code while it's being edited, to ensure that it compiles with SCP and is deployable?
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. First map where CDK code is edited in the VS Code toolkit and how SCP compliance and deployability are evaluated. Done means non-compliant code is flagged while editing and the requested validation is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript, vscode
- Domain
- cloud, devtools, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100