-
Epic
-
Resolution: Obsolete
-
Undefined
-
None
-
None
-
None
-
Enforce immutability for HC and NodePool API
-
False
-
False
-
To Do
-
Impediment
-
0
-
0
-
0
Context:
https://coreos.slack.com/archives/C01C8502FMM/p1626816698218800
Since IBM shared performance concerns at scale while using webhooks we decided to consider other approaches for enforcing fields immutability.
DoD:
We need to:
- Audit the whole API. Decided what’s immutable and what’s not.
- Discuss and agree on the implementation approach.
- Implement it.
We could run webhooks as an optional component and let it be a consumer choice to run them.
Alternatively the implementation could be based on having status as the source of truth for immutable fields.
1.
|
Docs Tracker | Closed | Unassigned | ||
2.
|
QE Tracker | Closed | Unassigned | ||
3.
|
TE Tracker | Closed | Unassigned |