0.0.5

feat: Add dynamic tagging and descriptions (#7)

This change will allow us to have a dynamic allocation of tags and project
descriptions. Within the example map file, the DDI information will be
defined as tag the tags allow projects to be searched.

The change asserts that defined tags will always be set whenever a user is
authenticated against a cloud with the plugin enabled.

``` shell
openstack --os-cloud default project show --domain rackspace_cloud_domain 1342135_Flex
+-------------+----------------------------------+
| Field       | Value                            |
+-------------+----------------------------------+
| ddi         | 1342135                          |
| description | Project for DDI 1342135          |
| domain_id   | 61ad3a247515421aaeaba18ae35aa095 |
| enabled     | True                             |
| id          | de15709c1cd242a6b7451d43c52d1640 |
| is_domain   | False                            |
| name        | 1342135_Flex                     |
| options     | {}                               |
| parent_id   | 61ad3a247515421aaeaba18ae35aa095 |
| tags        | ['1342135']                      |
+-------------+----------------------------------+
```

As seen in the above snippet, the project is now fully tagged, and labeled
based on the mapping. Additionally admins can now search projects using the
DDI as a tag,

``` shell
openstack --os-cloud default project list --domain rackspace_cloud_domain --long --tags 1342135
+----------------------------------+--------------------------------------+----------------------------------+-------------------------+---------+
| ID                               | Name                                 | Domain ID                        | Description             | Enabled |
+----------------------------------+--------------------------------------+----------------------------------+-------------------------+---------+
| 31a43637efc24ea19eea40af4e72d43d | 3965512c-e2c0-48a7-acef-3cdfb2b95ef8 | 61ad3a247515421aaeaba18ae35aa095 | Project for DDI 1342135 | True    |
| de15709c1cd242a6b7451d43c52d1640 | 1342135_Flex                         | 61ad3a247515421aaeaba18ae35aa095 | Project for DDI 1342135 | True    |
+----------------------------------+--------------------------------------+----------------------------------+-------------------------+---------+
```

Issue: https://rackspace.atlassian.net/browse/OSPC-746

Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>

0.0.4

feat: update keystone-rxt to use the new rxt role (#6)

This change makes it possible to run the keystone rxt plugin in
an environment using the os_flex attribute.

This change includes
* multi-account detection and autoprovisioning
* new mapping defaults for scheme version 2.0

Two new options have been added to support the creation of the
role attribute methods, allowing a user to be a member of more
than one project.

[rackspace]
role_attribute_enforcement <BOOL>
role_attribute <STR>

Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>

0.0.3

What's Changed

• Update after repo move by @cloudnull in #1
• ignore non-OpenStack Rackspace products by @cardoe in #2
• ci: publish tags to PyPi and make GitHub releases by @cardoe in #3

New Contributors

• @cloudnull made their first contribution in #1
• @cardoe made their first contribution in #2

Full Changelog: 0.0.2...0.0.3

Feature Complete POC

Add Multi-factor auth and caching

The keystone-rxt plugin will now allow a user to auth with passwords,
apikeys, and leverage multi-factor auth following the multifactor
authentication standards implemented by Rackspace Identity. These
improvements make it possible for all users of Rackspace Identity to
leverage an OpenStack environment with their existing credentials,
in the way that best suits their requirements.

On top of the interaction features this change also adds caching,
which will ensure we're able to efficiently interact with Rackspace
Identity without creating an authentication storm. The plugin will
now pull the service catalog from Rackspace Identity when needed
and then inspect the expires time, should the cached catalog expire,
a new one will be pulled. The same is true for the sessionID used
when dealing with multi-factor auth. Because Rackspace MFA requires
two requests, caching the session will allow us to shortcut the
number of repeat calls being made should a user run many commands
in short order. The caching implementation is fairly basic, but
extends our current capabilities and ensures good user experiences.

Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>

0.0.1

Initial Release