[compliance] User-defined regional constraint on workspace-cluster selection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
We have a limitation due to contractual/regulation limitations that require source code to always stay within the United States. As such, we need an ability to ensure that the environment we are deployed to at any time is only within the United States.
Describe the behaviour you'd like
Ideally, on a per-repository basis, we could select which data center we want to utilize, this would then limit the deployment to that data center.
Describe alternatives you've considered
For us, without this ability we will not be able to use the product at all, there is no workaround available.
Additional context
This is a requirement for many individuals developing solutions for government clients, or those that have things such as Export Compliance to worry about with encryption technology.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how repositories select workspaces and clusters, then identify where deployment location can be constrained. Done means a per-repository choice limits environments to the selected data center or region, including a United States-only option for compliance requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100