[FEAT-API Lambda]: Handle cascading Lambda effects
Open
@martyheynbah is already working on this.
Since Jul 8, 2026.
5SP
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If a user soft deletes or archives a LCG Lamnda, this then in turn invalidates all of the hydrograph sets that used this lcg outputs and then in turn all of the eurotop lambda runs that used the hydrograph set.
- lcg lambda output archived -> hydrograph sets corrupted -> eurotop lambda corrupted
How to handle keeping old output
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.
Assessment
This issue has not been assessed yet.