1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: I3564d1e10aeea40b74ef52bf29b3a39c5d9b0bc2
As part of allowing projects to establish redirects when they move
documentation pages around, we need to let them use .htaccess files.
We only want to allow Redirect and RedirectMatch directives,
though. This change restricts the directives on docs.o.o and adds them
on the static servers used for drafts published during a build (to
allow testing of the redirects).
For more details see:
http://lists.openstack.org/pipermail/openstack-dev/2017-July/120240.html
Change-Id: I754c8016ca2a475e74023017530264e7ae331557
This change moves existing files.
It is not meant to be the final word on how the main page looks or how the
other files are organized, but it gets everything roughly into shape. If
the barbican team wants to make changes, please do those as follow-up patches.
Note this does not touch the api directory, this one needs to be
migrated to the api-ref.
This is part of the docs migration work for Pike.
Change-Id: Ibb9d971806964ac185882272514ee9563089d69d
In the index.rst file, sometime, we declare that name_of_file.rst,
sometime is name_of_file.
For example. the content of the barbican/doc/source/api/index.rst
is that:
"""
./reference/secrets
./reference/secret_types
./reference/secret_metadata
./reference/store_backends.rst
./reference/containers
./reference/acls
./reference/quotas
./reference/consumers
./reference/orders
"""
That is confusing, it should be like below:
"""
./reference/secrets.rst
./reference/secret_types.rst
./reference/secret_metadata.rst
./reference/store_backends.rst
./reference/containers.rst
./reference/acls.rst
./reference/quotas.rst
./reference/consumers.rst
./reference/orders.rst
"""
Change-Id: I54ca41bb27f59caaaddab977ef4a3cf7f66bb5f3
Closes-Bug: #1694180
Resolves some errors in the Consumer API Reference Documentation
including improper requests and missing headers. Also Updates
response codes.
Depends-On: Ib038047dc1b96194ea1b5ff63ae58b5c78d05ffd
Related-Bug: #1660074
Change-Id: I6f1af0b95d3800bf182f4d6bebcdebb8eb60ddd7
This change breaks several gates, including RDO's package promotion.
This reverts commit f06ba481956d406a1edf644f1c2c3ff55705d0f1.
Change-Id: I0524b7057016daa59ea0a506bdc50a71e9fc8f6a
This patch adds an "id" property to secrets, orders and containers
returned from the API. The value of the "id" property is the unique
UUID found at the end of the entity reference.
Change-Id: I65bab35807ed2cee6ed5d6aca1c99769678751be
Begins the deprecation process for Barbican CAs API,
and Barbican Certificate Orders Resource. This is
done through logging deprecation schedule on API,
as well as adding a warning to the documentation.
Change-Id: Idbe6307fa45527aa225e61b3b1ac9ca86e7660c5
Added tests to provide 100% coverage on API and policy logic.
Change-Id: Icb43049250be1d78bdd3db8fbad0dc0381cccaf7
Partially-Implements: blueprint multiple-secret-backend
There are a few places in our documentation where we use lowercase
'url'. This CR changes those to 'URL' for consistency.
Change-Id: I509fd82f1a44bfbc819866a45aaffafb0192bc36
Modified policy and tests to verify this change.
As per this change, user with 'creator' role can delete a secret or
a container as long as that user has initially created that secret
or container.
There is still a difference between 'admin' role and 'creator' role
behavior around delete operation. With this change, users with 'creator'
role cannot delete any other user's secret/container in same project
while user with 'admin' role can do that.
Updated role docs to reflect this behavior.
Change-Id: I53e5529ed34ac4acc76348ca0431cb3de7934b6d
This configures Barbican to use Keystone authentication by
default and updates documentation accordingly.
Change-Id: Ie0a1995b971371d18238138575629eeee1a36392
Closes-Bug: #1595428
This adds POST and DELETE support for a 'secrets' sub-resource on the
containers resource. This will allow a user to add or remove secret
references to an existing container. Only generic containers are
supported per the blueprint for this feature.
If a secret reference already exists in the container, an appropriate
error will be returned indicating that the secret already exists in
the container. I chose this approach over silently accepting the
update, as the name for the container secret could change, so a delete
and re-add seems to be the safer option if a user just wants to change
the name, which is not something that I see happening too often.
Additionally, the action is a POST and not a PUT, so it shouldn't
really update an existing resource.
APIImpact
Add support for POST and DELETE on container secrets sub-resources
DocImpact
Implements: blueprint api-containers-add-put
Change-Id: I6dfa6715385f421e4f173cf73c2b75b68da67051
When building the docs using `tox -e docs`, several warning messages
would print out. This change fixes the issues causing those warnings.
Change-Id: I57503c75f6c07c020bb3bfa34de6aa8f66983ff7
keystonemiddleware admin settings are deprecated
so we should stop using them in favor of a keystone
auth plugin. This patch updates the config file
to use keystone API v3 by default.
Change-Id: I9d10ac29ab33cbdd845573106960e5f181afdb69
Closes-Bug: 1579801
Moving files from doc/source/api/userguide/*.rst
to api-guide/source/*.rst,
also add api-guide/source/conf.py for building api-guide,
add a new tox target named api-guide
Taking a reference from this patch which was used for the
similar migration of Nova api guide:
https://review.openstack.org/#/c/230186
Change-Id: I725e7939f9a88185de6ef32b311159b0924b7183
Partial-Bug: #1540665
Needed-By: I7b7c623e6299c803930e41d72510f1a67d909fa3
