You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when we autogenerate reference doc for policy we do it from generic API for policy, so all targetRefs can accept all kinds, also we list all fields from targetRef. This ends up with a situation where our customers try to build policies based on this reference, but they end up debugging their policies based on errors from validators.
Expected behavior
We should properly generate this reference, or we should generate reference only for default fields which contains actual configuration of given policy
Triage: For now. we are going to remove targetRef from this place and we can link to the targetRef docs. Future, should we have policy-specific targetRef docs(manually or automatically )? After removing an open issue to improve policy specific targetRef
Kuma Version
all
Describe the bug
Right now when we autogenerate reference doc for policy we do it from generic API for policy, so all targetRefs can accept all kinds, also we list all fields from targetRef. This ends up with a situation where our customers try to build policies based on this reference, but they end up debugging their policies based on errors from validators.
Expected behavior
We should properly generate this reference, or we should generate reference only for
default
fields which contains actual configuration of given policyAdditional context (optional)
https://kongstrong.slack.com/archives/C0164PPUSFP/p1738887785829129
https://kuma.io/docs/2.9.x/policies/meshloadbalancingstrategy/#all-policy-options
The text was updated successfully, but these errors were encountered: