Project

General

Profile

Bug #6647

Foreman organization API destroy routes (DELETE /api/v2/organizations/1 and DELETE /api/v1/organizations/1) are still accessible

Added by Eric Helms about 7 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Related issues

Related to Katello - Bug #6707: Remove or update the V1 APIRejected2014-07-21
Related to Katello - Bug #6708: Have the /api/v2/organization routes point to our Organization controller in KatelloRejected2014-07-21
Related to Foreman - Feature #9375: Find a way for plugins to easily override the behavior of taxonomies controller actionsRejected2015-02-13

Associated revisions

Revision 0a139060 (diff)
Added by David Davis about 7 years ago

Fixes #6647,BZ1120335 - Remove old foreman org destroy routes

Removing old foreman destroy routes since they don't use dynflow to delete
organizations.

Revision 9919e0ba
Added by David Davis about 7 years ago

Merge pull request #4463 from daviddavis/temp/20140721155712

Fixes #6647,BZ1120335 - Remove old foreman org destroy routes

History

#1 Updated by Partha Aji about 7 years ago

  • Bugzilla link set to 1120335

#2 Updated by David Davis about 7 years ago

  • Priority changed from Normal to Low

#3 Updated by The Foreman Bot about 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4441 added
  • Pull request deleted ()

#4 Updated by David Davis about 7 years ago

  • 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)

#5 Updated by David Davis about 7 years ago

  • 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.

#6 Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4463 added
  • Pull request deleted ()

#7 Updated by David Davis about 7 years ago

  • Assignee set to David Davis

#8 Updated by David Davis about 7 years ago

  • Related to Bug #6707: Remove or update the V1 API added

#9 Updated by David Davis about 7 years ago

  • Related to Bug #6708: Have the /api/v2/organization routes point to our Organization controller in Katello added

#10 Updated by David Davis about 7 years ago

  • 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.

#11 Updated by David Davis about 7 years ago

  • Priority changed from Low to Normal

#12 Updated by David Davis about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#13 Updated by Eric Helms about 7 years ago

  • Legacy Backlogs Release (now unused) set to 13

#14 Updated by David Davis over 6 years ago

  • Related to Feature #9375: Find a way for plugins to easily override the behavior of taxonomies controller actions added

Also available in: Atom PDF