uselagoon / uselagoon/remote-controller
Fail build on any errors produced by the controller
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
Currently if a step in provisioning the build by the controller fails, it can get stuck in a state where it may keep trying.
Instead of returning an error and re-trying, the build should fail and report back that it has failed to Lagoon.
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
Trace the controller's build-provisioning flow and find where step errors are returned and retried. Confirm how the controller reports build status back to Lagoon, then verify that any provisioning error produces a failed build instead of another retry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100