Plan preview diff is incorrect if manifest gets values dynamically
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
When plan preview is executed, "previous" manifests are created on the fly with the last commit of the successful deployment. This process can create different manifests from the actual "previous" manifest if templating tools get values dynamically. e.g. Getting the latest helm charts.
What you expected to happen:
How to reproduce it:
Environment:
pipedversion:control-planeversion:- Others:
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 tracing the plan preview flow that reconstructs the previous manifest from the last successful deployment. Compare that generated manifest with the actual previous manifest when templating tools, such as Helm charts, resolve dynamic values. Done means plan preview diffs use the correct previous state instead of a newly rendered variant.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100