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
Redpanda version: (use rpk version): v23.3.5
rpk version
I created a transform with name some-transform/name that&requires! encoding and was unable to delete it using:
some-transform/name that&requires! encoding
curl -i -X "DELETE" http://localhost:65193/v1/transforms/some-transform%2Fname%20that%26requires%21%20encoding HTTP/1.1 404 Not Found Content-Length: 37 Server: Seastar httpd Date: Mon, 19 Feb 2024 16:04:42 GMT Content-Type: application/json {"message": "Not found", "code": 404}%
It should have unescaped the parameter so that it matches the transform that I created previously.
This seems to be a common bug in the admin API. See:
curl -s http://localhost:65193/v1/transform | jq . [ { "name": "test-get-tf", "input_topic": "wasm-tfm-create-test-c", "output_topics": [ "wasm-tfm-create-test-d" ], "status": [ { "node_id": 0, "partition": 0, "lag": 0, "status": "running" }, { "node_id": 0, "partition": 1, "lag": 0, "status": "running" } ], "environment": [ { "key": "foo", "value": "bar" } ] }, { "name": "some-transform/name that&requires! encoding", "input_topic": "wasm-tfm-create-test-c", "output_topics": [ "wasm-tfm-create-test-d" ], "status": [ { "node_id": 0, "partition": 0, "lag": 0, "status": "running" }, { "node_id": 0, "partition": 1, "lag": 0, "status": "running" } ], "environment": [ { "key": "foo", "value": "bar" } ] } ]
The text was updated successfully, but these errors were encountered:
rockwotj
Successfully merging a pull request may close this issue.
Version & Environment
Redpanda version: (use
rpk version
): v23.3.5What went wrong?
I created a transform with name
some-transform/name that&requires! encoding
and was unable to delete it using:What should have happened instead?
It should have unescaped the parameter so that it matches the transform that I created previously.
How to reproduce the issue?
Additional information
This seems to be a common bug in the admin API. See:
The text was updated successfully, but these errors were encountered: