[Bug]: API's context can't be updated in On-Prem
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Start by tracing the REST API overview edit flow and the API context update request through the platform API backend. Reproduce the issue by changing the context, saving, and refreshing; check where the saved value is handled. Done when the updated context persists after refresh.
Written by the indexing model from the issue text.
Description
Please select the area the issue is related to
Platform API
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
Editing the context of the API is not updating it.
Steps to Reproduce
- Create a REST API.
- Go to the edit menu from the overview page.
- Edit the context and save it.
- Check the context value after refreshing.
Severity Level of the Issue
Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)
Environment Details (with versions)
No response
- Dominant language
- Go
- Stars
- 76
- Forks
- 126
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 181
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wso2/api-platform
-
Aspect/API Severity/Minor Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
wso2/api-platform#3885 · 1 comment ·
Maintainers usually reply within 1 day
-
Aspect/API Severity/Minor Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wso2/api-platform#3884 · 1 comment ·
Maintainers usually reply within 1 day
-
Aspect/API Severity/Minor Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wso2/api-platform#3882 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: Deleting an MCP proxy leaves its API keys in the gateway's memory and in the policy engineOpenAspect/API Aspect/Other Severity/Minor Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
wso2/api-platform#3852 ·
Maintainers usually reply within 1 day
-
[Bug]: Policy-engine sampler ignores the parent's sampling decision, producing orphan spans and partial tracesPossibly taken @lahiruudayakumara claimed this 10 days ago. OpenArea/Gateway Aspect/Monitoring Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wso2/api-platform#3735 ·
Maintainers usually reply within 1 day
All issues in wso2/api-platform
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
kind/engineering pulumi/pulumi-terraform Task Workflow Failure
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
pulumi/pulumi-terraform#1261 ·
Maintainers usually reply within 1 day
-
Controllers integration tests fail when port 8080 is in usePossibly taken @noahnut claimed this today. Openarea/cluster-autoscaler kind/bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubernetes-sigs/cluster-autoscaler#236 · 1 comment ·
Maintainers usually reply within 1 day
-
MCP: `tasks_bulk_update` always fails with "Need at least one field" — the `fields` projection argument is stripped from non-read tools tooPossibly taken @tink-bot claimed this today. Openagent-processed area/api-v2 integration/inbound
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
go-vikunja/vikunja#4235 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
google/osv-scalibr#2503 ·
Maintainers usually reply within 1 day