deckhouse / deckhouse/deckhouse-cli
Move DeckhouseRelease manifests generation step earlier in d8 mirror pull
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 7
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 33
Description
Use case. Why is this important?
Currently, when running:
d8 mirror pull <bundle> --license <TOKEN> --since-version <VERSION>
the step Generating DeckhouseRelease manifests is executed after pulling all release channels and installers. For large bundles, this means waiting before the file deckhousereleases.yaml appears, even though it depends only on release-channel metadata.
This behavior makes it inconvenient to: quickly obtain deckhousereleases.yaml, generate release manifests.
Proposed Solution
Move the Generating DeckhouseRelease manifests step up in the execution order:
Generate deckhousereleases.yaml immediately after pulling release channels, before pulling heavy artifacts.
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 with the d8 mirror pull execution flow and locate the step that pulls release channels and the step that generates deckhousereleases.yaml. Move manifest generation to immediately follow release-channel pulling, before heavy artifacts are fetched, and verify the file appears at that point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100