| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch will allow the python-barbicanclient to perform
Secret Updates. This functionality will also be added to the
barbican command line client. I will also allow for a secret
to be created without a payload.
Change-Id: Ia53e1cc463f9a274feb11f6e3bb3cbbe981c3444
|
| |/
|
|
|
|
|
|
|
| |
Other clients have an epilogue at the end of the parser
that shows up when the help flag is used. This adds the
epilogue to aid in using the barbican client.
Documentation is updated as well.
Change-Id: I0463aa5c980e8337fb06e70c083763fddb2c0746
|
| |
|
|
|
|
|
|
|
| |
The README file needs to have links to the project documentation and bug
tracker in a parsable format in order for some of the release tools
scripts to work (particularly the one that prints the release note
email).
Change-Id: I04c11e311b5d1610249ceacc2572f39851aef0ea
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Deprecate manually setting the payload_content_type and
payload_content_encoding properties of a secret. With this CR a user of
the client only needs to provide the payload, and the client will figure
out what the correct payload_content_type and payload_content_encoding
values should be.
Setting these properties for the user lets us avoid a lot of weird
behaviors such as the one described in Bug #1419166, and also lets us
avoid errors that happen when a user mismatches the payload and an
incorrect content type.
In the interest of backwards compatibility, these properties are still
usable, but will log deprecation warnings. They should be removed in a
future version after current users have had enough time to update their
code bases.
Change-Id: Ibfe3ad42e11bd83c002d0f1b69fb8a323a7b6f3d
Closes-Bug: #1419166
|
| |
|
|
|
|
|
| |
Updated README to point to the official OpenStack docs for the client.
Also fixed a typo in the authentication page.
Change-Id: I81696138cfa929efd7074b52edde8d4019e2fd50
|
| |
|
|
|
|
| |
Added sphinx documentation source skeleton from cookiecutter.
Change-Id: I7c9fa2c0668b93dd00eecca90617121fdae304ea
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CR changes the Client to use Keystone Sessions exclusively. All
authentication that was previously available in barbicanclient is
removed so that we can defer all authentication to keystoneclient.
Unit tests for the client module have been refactored to test the new
functionality.
The README file has been updated to give an example of how to
authenticate with Identity v3 using Sessions.
The Client will now give priority to an endpoint that is passed in over
endpoints found in the service catalog, which closes bug #1276002. This
is helpful for development, where you might be running an instance of
Barbican locally that uses a Keystone instance for authentication that
does not have the Barbican service in its catalog.
The CLI uses Keystone API v3 as the default authentication method, but
can also use v2.0.
DocImpact
Implements: blueprint use-keystone-sessions
Closes-Bug: #1276002
Change-Id: I9d07cb50143c1f5cafea48318018a205f745999f
|
| |
|
|
|
| |
Change-Id: I330443029cf600e17f0bbaf11143577139985f49
Closes-bug: #1323830
|
|
|
Change-Id: I0fd5d1efacada53260097d18405dc863110c89ae
|
