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
From parameterizing the Kubernetes Object Trigger, it would seem that parameter values are casted to strings, even when in source they are number. My use case calls for creating Traefik IngressRoutes when new Services are detected, and for reusing port numbers. Is string the only value type supported by parameterization?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
From parameterizing the Kubernetes Object Trigger, it would seem that parameter values are casted to strings, even when in source they are number. My use case calls for creating Traefik IngressRoutes when new Services are detected, and for reusing port numbers. Is string the only value type supported by parameterization?
Also tried object type, however trigger fails.
Beta Was this translation helpful? Give feedback.
All reactions