KusionStack / KusionStack/kusion
Feat: Kusion module supports Non-AppConfiguration model as generator entrance
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 107
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
What would you like to be added?
kusion-module-framework supports Non-AppConfiguration model as generator entrance.
Why is this needed?
Currently, the entry point for Kusion module generator is unified as AppConfiguration, but users might have orchestration requirement for resource groups that are Non-AppConfiguration. Therefore, kusion-module-framework needs to provide support for this.
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 locating the kusion-module-framework generator entry point and the current AppConfiguration handling. Trace how resource groups are accepted and generated, then determine the intended contract for Non-AppConfiguration models. Done means a non-AppConfiguration model can serve as a generator entrance, with coverage for that path in the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100