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
Error: reading Kong version: making HTTP request: Get "http://localhost:8001/": dial tcp [::1]:8001: connect: connection refused
In the above use case, the user is trying to ping konnect, however, the error message appears to be responding to the default --kong-addr value which is a self-managed setup ( and a completely different URL )
Analysis
The problem in this case is that decK has no way to determine whether the user wanted to ping Konnect or Kong: the https://us.api.konghq.com value passed via the --konnect-addr is the default one decK uses for Konnect, so the command the customer ran is actually equivalent to just deck ping.
Acceptance Criteria
Detect the presence of --konnect-addr using viper.isSet and change the error message as needed
All commands detect --konnect-addr being provided, not just deck ping
The text was updated successfully, but these errors were encountered:
mheap
changed the title
Check if --konnect-addr is set in deck ping
Check if --konnect-addr is set
Sep 6, 2024
Previously, if a deck command was issued with --konnect-addr flag
but with the default konnectUrl https://us.api.konghq.com, the
flag value was getting ignored as deck could not figure out
if it was passed by flag or not. This change ensures that if the
flag is set, deck commands are issued against Konnect.
Fixes: #1385
Using the command
returns the error message
In the above use case, the user is trying to ping konnect, however, the error message appears to be responding to the default --kong-addr value which is a self-managed setup ( and a completely different URL )
Analysis
The problem in this case is that decK has no way to determine whether the user wanted to ping Konnect or Kong: the https://us.api.konghq.com value passed via the --konnect-addr is the default one decK uses for Konnect, so the command the customer ran is actually equivalent to just deck ping.
Acceptance Criteria
--konnect-addr
usingviper.isSet
and change the error message as needed--konnect-addr
being provided, not justdeck ping
The text was updated successfully, but these errors were encountered: