We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HI, we noticed into deck 0.6.0 an issue during the sync operation, the workspace hasn't been recognized from the APIs but it's present. The output is:
# deck sync --kong-addr http://admin.test.local :8080 --state kong-internal.yml --verbose 1 --parallelism 1 GET /workspace/workspace-test HTTP/1.1 Host: admin.test.local :8080 User-Agent: Go-http-client/1.1 Accept-Encoding: gzip HTTP/1.1 404 Not Found Content-Length: 23 Access-Control-Allow-Credentials: true Access-Control-Allow-Origin: http://admin.test.local Connection: keep-alive Content-Type: application/json; charset=utf-8 Date: Mon, 04 Nov 2019 15:10:11 GMT Server: kong/0.35-3-enterprise-edition Vary: Origin {"message":"Not found"} Error: workspace 'workspace-test' does not exist in Kong, please create it before running decK.
The error is related to a wrong API call to "/workspace" instead "/workspaces/".
Marcello
The text was updated successfully, but these errors were encountered:
Confirmed. Will be fixed with v0.6.1
Sorry, something went wrong.
fix(cmd) corret url to /workspaces/:workspace
3762536
Fix #94
17a7342
78c17ac
6f0aaf3
Successfully merging a pull request may close this issue.
HI,
we noticed into deck 0.6.0 an issue during the sync operation, the workspace hasn't been recognized from the APIs but it's present. The output is:
The error is related to a wrong API call to "/workspace" instead "/workspaces/".
Marcello
The text was updated successfully, but these errors were encountered: