Bug 1396913
| Summary: | [RFE] CLI to create Keystone trusts | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Dan Callaghan <dcallagh> |
| Component: | general | Assignee: | Roman Joost <rjoost> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | develop | CC: | dcallagh, dowang, mjia, rjoost |
| Target Milestone: | 24.0 | Keywords: | FutureFeature, Patch |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-21 18:50:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dan Callaghan
2016-11-21 07:01:28 UTC
We could re-use the bkr update-prefs subcommand, although that feels a bit awkward since the trust id itself is not a preference (instead you supply username, password, and project name in order to obtain a new trust id). So I guess we are better off with a new subcommand: bkr update-keystone-trust --os-username=... --os-password=... --os-project-name=... Or maybe, bkr update-openstack-trust? The update will simply use the PUT rest api endpoint and values will simply be overwritten with the ones provided by the user. Currently the API expects a username. I'll add an additional endpoint resolving to +self which will use the currently authenticated user. Patch available: https://gerrit.beaker-project.org/#/c/5462/3 Beaker 24.0 has been released. |