Bug 743098
| Summary: | RFE: API results for channel.software.clone does not match channel.software.getDetails | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | lance dillon <ldillon> |
| Component: | API | Assignee: | Tomas Lestach <tlestach> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.5 | CC: | slukasik |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-23 10:02:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 737830 | ||
Yes, I like this RFE. I changed the channel.software.clone API parameters to use: gpg_key_url, gpg_key_id and gpg_key_fp. However, the original parameters are still usable because of compatibility reasons. spacewalk.git: f95263e9b019d791941942e2ec262c4709f14f74 Spacewalk 1.6 has been released. |
Description of problem: API results for channel.software.clone does not match channel.software.getDetails. getDetails returns gpg_key_{fp,id,url}, but clone takes gpg_{url,id,fingerprint} instead. This requires programming to convert one to the other (if you are copying that info also) instead of just being able to assign/copy the details. Version-Release number of selected component (if applicable): 1.5 How reproducible: Call channel.software.getDetails, notice that result has gpg_key_{fp,id,url}, but http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.4/html/API_Overview/handlers/ChannelSoftwareHandler.html#clone says: string "gpg_url" - (optional) string "gpg_id" - (optional) string "gpg_fingerprint" - (optional) Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Not sure I have expected results other than would like the names to be the same so that programmatically it is easier to deal with those values. Additional info: It may not be possible to change if too many things are using the api as it is. This is really a low priority item, more of a "Would be nice..." than a bug.