Bug #6708
Have the /api/v2/organization routes point to our Organization controller in Katello
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Related issues
History
#1
Updated by David Davis almost 8 years ago
- Related to Bug #6647: Foreman organization API destroy routes (DELETE /api/v2/organizations/1 and DELETE /api/v1/organizations/1) are still accessible added
#2
Updated by David Davis almost 8 years ago
Optimally we want to keep the foreman routes instead of defining new Katello ones. Currently in Katello the api org routes are at
/katello/api/v2/organizations
#3
Updated by Partha Aji almost 8 years ago
- Bugzilla link set to 1122678
#4
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Target version set to 49
- Pull request https://github.com/Katello/katello/pull/4486 added
- Pull request deleted (
)
#5
Updated by Eric Helms almost 8 years ago
- Difficulty set to easy
- Triaged changed from No to Yes
#6
Updated by Eric Helms almost 8 years ago
- Target version changed from 49 to 54
#7
Updated by Eric Helms almost 8 years ago
- Target version changed from 54 to 55
#8
Updated by David Davis almost 8 years ago
- Status changed from Ready For Testing to Rejected
This is probably not going to make it in 2.0 so I'm going to reject it. I think being consistent over releases is better than pleasing foreman API users who upgrade to foreman + katello.
#9
Updated by Eric Helms almost 8 years ago
- Legacy Backlogs Release (now unused) set to 13
#10
Updated by David Davis over 7 years ago
- Related to Feature #9375: Find a way for plugins to easily override the behavior of taxonomies controller actions added
#11
Updated by Eric Helms about 7 years ago
- Legacy Backlogs Release (now unused) deleted (
13)
#12
Updated by Eric Helms almost 6 years ago
- Legacy Backlogs Release (now unused) set to 166