Bug 1118473 - [RFE] provide easy method to retrieve oauth goo necessary for installing capsules.
Summary: [RFE] provide easy method to retrieve oauth goo necessary for installing caps...
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Hammer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-10 20:02 UTC by Corey Welton
Modified: 2017-11-30 19:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2017-11-30 19:27:39 UTC

Attachments (Terms of Use)

Description Corey Welton 2014-07-10 20:02:47 UTC
Description of problem:
If I want to programmatically automate installation of a bunch of capsules for a sat instance, I have to dig through various foreman/pulp config files to get all the proper oauth keys and secrets, etc.

When we create a cert for a capsule (capsule-certs-generate), we are provided text that [sort of] explains what parameters need to be populated, including the oauth secret/keys.  So we have a way to retrieve this.

It would be nice if we had a command -- via hammer, or via some other method -- to simply output these in raw text pairs or json or something so that it is easier to script the installation of a bunch of capsules

Comment 1 Corey Welton 2014-07-10 20:05:17 UTC
In the MDP2 days, when we had 'nodes', for example, it was easy enough to cat /etc/katello/oauth_token-file.  Now we have more tokens/secrets and they are buried deeper in config files.  Just a simple way to retrieve all these would be suitable.

Comment 5 Bryan Kearney 2017-11-30 19:27:39 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Note You need to log in before you can comment on or make changes to this bug.