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
decK v0.4.0 changed the default for strip_path to be false. The default for Kong however is for the default to be true.
I would argue that decK simply should not set a default, and leave the value empty if not explicitly set by the user.
The original issue (which introduced this change) was about not being able to set the value to false at all.
Unfortunately the fix for this also changed the default value to false.
The description in the commit reads
Breaking change:
This is a limitation of how we fill in default values for the missing
values. It is not possible in Go to determine if a value is nil vs a
zero vaule (false for boolean).
Is there any other way to fix this?
This issue broke our Kong db-less to db-based migration, as the yaml configs imported via decK suddenly observed a different default behavior.
Issue description
decK v0.4.0 changed the default for
strip_path
to befalse
. The default for Kong however is for the default to betrue
.I would argue that decK simply should not set a default, and leave the value empty if not explicitly set by the user.
The original issue (which introduced this change) was about not being able to set the value to
false
at all.Unfortunately the fix for this also changed the default value to false.
The description in the commit reads
Is there any other way to fix this?
This issue broke our Kong db-less to db-based migration, as the yaml configs imported via decK suddenly observed a different default behavior.
Links
The text was updated successfully, but these errors were encountered: