It looks like the new dumpconfig.sh CLI isn't constructing the URL correctly, by omitting the mandatory profile query parameter.
This results in a MessageDecodingException error in the logs, but the result seen by the dumpconfig cli is a 400 error. I'm guessing a failure to decode always results in a 400 for "I don't want to be an oracle" security reasons but if we weren't concerned about that in this case there are probably better HTTP codes to return.
It looks like the new
dumpconfig.shCLI isn't constructing the URL correctly, by omitting the mandatory profile query parameter.This results in a
MessageDecodingExceptionerror in the logs, but the result seen by the dumpconfig cli is a 400 error. I'm guessing a failure to decode always results in a 400 for "I don't want to be an oracle" security reasons but if we weren't concerned about that in this case there are probably better HTTP codes to return.Manually constructing the URL does seem to work.