Missing functionality that Kong Declarative Config supports #123
Comments
hbagdi
added a commit
that referenced
this issue
Feb 7, 2020
`url` property is deconstructed on file read into protocol, host, port and path. There are checks in place but this is likely not going to be full-proof and the code will break in corner cases if all the components are not specified. It should suffice for most use-cases. Fix #123
rainest
pushed a commit
that referenced
this issue
Apr 21, 2021
`url` property is deconstructed on file read into protocol, host, port and path. There are checks in place but this is likely not going to be full-proof and the code will break in corner cases if all the components are not specified. It should suffice for most use-cases. Fix #123
AntoineJac
pushed a commit
that referenced
this issue
Jan 23, 2024
`url` property is deconstructed on file read into protocol, host, port and path. There are checks in place but this is likely not going to be full-proof and the code will break in corner cases if all the components are not specified. It should suffice for most use-cases. Fix #123
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears there is more missing than just the header as explained in #26
Deck does not support sugar features, one being the Service
url, which is supported by both the API and Kong Declarative Config, and is preventing us from using deck in production.The text was updated successfully, but these errors were encountered: