livecycle / livecycle/deploykit
GCP Config Connector CRDs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi ! First of all, great work with deploykit. I am quite aligned on this approach have been using deploykit's k8s generated API here: https://github.com/dxcfg/dxcfg.
I see a potential use case to provision GCP resources using config connector [CRDs](https://github.com/GoogleCloudPlatform/k8s-config-connector/tree/master/crds). Would you be open to a contribution for that ?
Contributor guide
No contributing guide indexed for this repository
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 reviewing deploykit's Kubernetes generated API and the linked Google Cloud Config Connector CRDs. The issue does not define which GCP resources or generated outputs are in scope, so completion criteria would need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, gcp, kubernetes, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100