Bug #6647
closed
Foreman organization API destroy routes (DELETE /api/v2/organizations/1 and DELETE /api/v1/organizations/1) are still accessible
Added by Eric Helms about 10 years ago.
Updated about 6 years ago.
- Bugzilla link set to 1120335
- Priority changed from Normal to Low
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/4441 added
- Pull request deleted (
)
- Status changed from Ready For Testing to New
- Assignee deleted (
David Davis)
- Pull request added
- Pull request deleted (
https://github.com/Katello/katello/pull/4441)
- Subject changed from Organization destroy API (/api/v2/organizations/1) does not use dynflow destroy to Foreman organization API (e.g. /api/v2/organizations/1) is still accessible
I was trying to approach this by pointing the route at the katello org controller. However, I think the better solution though is to remove the old routes. I don't think there should exist routes that aren't in our api docs.
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/4463 added
- Pull request deleted (
)
- Assignee set to David Davis
- Related to Bug #6707: Remove or update the V1 API added
- Related to Bug #6708: Have the /api/v2/organization routes point to our Organization controller in Katello added
- Subject changed from Foreman organization API (e.g. /api/v2/organizations/1) is still accessible to Foreman organization API destroy routes (DELETE /api/v2/organizations/1 and DELETE /api/v1/organizations/1) are still accessible
Making this more specific to org destroy since I need to also fix v1. Plus, #6708 should fix the Foreman organizations API.
- Priority changed from Low to Normal
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 13
- Related to Feature #9375: Find a way for plugins to easily override the behavior of taxonomies controller actions added
Also available in: Atom
PDF