google / google/stellar-engine
[Feature Request] Automate Project ID randomization for soft-delete mitigation
- Dominant language
- HCL
- Stars
- 49
- Forks
- 20
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 28
Description
## Feature Description
Append a randomized string to all generated Google Cloud Project IDs.
## Use Case
If a Google Cloud project is deleted, it enters a 30-day soft-delete lock. Terraform deployments currently fail if a developer attempts to redeploy to the same environment using the same project name.
## Proposed Solution
Integrate a `random_string` or `random_id` Terraform resource into the base project creation modules to append a 4-character unique hash to all generated Project IDs, preventing naming collisions.
## Compliance & Deployment Context
* **Target Deployment Type(s):**
* [ ] US Region Restricted (e.g., Access Policy constraint)
* [ ] FedRAMP Medium
* [ ] FedRAMP High
* [ ] DoD IL4
* [ ] DoD IL5
* [x] All / General
## Reusability Check
Stellar Engine prioritizes reusability.
* [x] I have checked if this functionality can be achieved by extending an existing module or blueprint.
* [x] I have verified that this does not duplicate existing functionality.
## Alternatives Considered
Forcing developers to manually change variable names every time they tear down and rebuild an environment.
## Additional Context
This was explicitly requested in the legacy Feature Braindump from 2023.
Contributor guide
Assessment
This issue has not been assessed yet.