google / google/stellar-engine
[Feature Request] Remove Source Repo references and modules and replace with SSM
- Dominant language
- HCL
- Stars
- 49
- Forks
- 20
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 28
Description
## Feature Description
This feature allows Secure Source Manager to used as an option for cicd and creates template triggers.
## Use Case
Cloud Source Repositories has been deprecated since 2024 and should not be used anymore. Secure Source Manager is the replacement service for it.
## Proposed Solution
Update all previous references to source repo in the cicd.tf files and modules to use SSM instead.
## Compliance & Deployment Context
* **Target Deployment Type(s):**
* [X] US Region Restricted (e.g., Access Policy constraint)
* [X] FedRAMP High
* [X] FedRAMP Moderate
* [ ] DoD IL4
* [ ] DoD IL5
* [] All / General
* **Relevant NIST 800-53r5 Controls:** (If applicable, list the controls this feature helps satisfy)
## 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
## Additional Context
Contributor guide
Research direction
Start by locating the cicd.tf files and modules containing Cloud Source Repositories or source repo references. Trace how those modules create CI/CD configuration and template triggers, then replace the identified references with Secure Source Manager integrations. Done means the old source-repo references are removed and the affected deployments support SSM-based triggers across the stated compliance contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, terraform
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100