-
Epic
-
Resolution: Won't Do
-
Normal
-
None
-
Add an option to configure the limit of the manifests in manifestwork
-
False
-
None
-
False
-
Not Selected
-
To Do
OCP/Telco Definition of Done
<https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde>
Epic Template descriptions and documentation.
<https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit>
ACM-wide Product Requirements (Top-level Epics)
<https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit>
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
Currently we have 50k limit for the manifests in a manifestWork, but there are some requirements from community that the size of manifests may exceed the limit, so we need to make the limit configurable.
suggest to add an option for the work webhook binary to configure the limit.
This epic is transferred from github https://github.com/stolostron/backlog/issues/26253
Why is this important?
...
Scenarios
1. The size of manifests in a manifestWork exceeds 50k, should deploy the manifestWork successfully.
Acceptance Criteria
- The cluster admin can configure the limit as an option.
- Any manifestWorks less than 50k can be deployed successfully.
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>