Merge pull request #52 from britive/develop

v0.10.0

Author: twratl

CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All changes to the package starting with v0.3.1 will be logged here.
 
+## v0.10.0 [2023-01-18]
+#### What's New
+* Support Bitbucket as a federation provider
+
+#### Enhancements
+* None
+
+#### Bug Fixes
+* None
+
+#### Dependencies
+* `britive~=2.14.0` from `britive~=2.13.0` - bitbucket federation provider
+
+#### Other
+* None
+
 ## v0.9.2 [2023-01-11]
 #### What's New
 * None

docs/index.md

@@ -89,10 +89,11 @@ At feature launch the following types of identity providers are supported for wo
 * Open ID Connect (OIDC)
 * AWS STS
 
-`pybritive` offers some native integrations with the following services at the launch of this feature.
+`pybritive` offers some native integrations with the following services.
 
 * Github Actions
 * AWS
+* Bitbucket
 
 It is possible to source an identity token from a different OIDC provider and explicitly set it via the `--token\-T` flag.
 However, if you are using one of the above providers, a shortcut is provided to abstract away the complexity of sourcing these tokens.
@@ -115,6 +116,9 @@ pybritive checkout "profile" --federation-provider aws  # use aws sts without an
 pybritive checkout "profile" --federation-provider aws-profile  # use aws sts with an AWS CLI profile
 pybritive checkout "profile" --federation-provider aws-profile_expirationseconds   # use aws sts with an AWS CLI profile and set the Britive expiration (in seconds) of the generated token
 pybritive checkout "profile" --federation-provider aws_expirationseconds  # use aws sts without an AWS CLI profile and set the Britive expiration (in seconds) of the generated token
+
+# bitbucket (note that no additional options are available for bitbucket)
+pybritive checkout "profile" --federation-provider bitbucket
 ~~~
 
 In general the field format for `--federation-provider` is `provider-[something provider specific]_[duration in seconds]`.

requirements.txt

@@ -1,4 +1,4 @@
-britive~=2.13.0
+britive~=2.14.0
 certifi==2022.6.15
 charset-normalizer==2.1.0
 click==8.1.3

setup.cfg

@@ -1,6 +1,6 @@
 [metadata]
 name = pybritive
-version = 0.9.2
+version = 0.10.0
 author = Britive Inc.
 author_email = support@britive.com
 description = A pure Python CLI for Britive
@@ -26,7 +26,7 @@ install_requires =
     toml
     cryptography
     python-dateutil
-    britive>=2.13.0
+    britive>=2.14.0
 
 [options.packages.find]
 where = src

src/pybritive/britive_cli.py

@@ -167,7 +167,7 @@ def print(self, data: object, ignore_silent: bool = False):
 
     def user(self):
         self.login()
-        username = self.b.my_access.whoami()['user']['username']
+        username = self.b.my_access.whoami()['username']
         alias = self.tenant_alias
         output = f'{username} @ {self.tenant_name}'
         if alias != self.tenant_name:

src/pybritive/options/federation_provider.py

@@ -3,8 +3,8 @@
 option = click.option(
     '--federation-provider', '-P',
     help='Use a federation provider available in the Britive Python SDK for auto token creation. '
-         'Valid values are `aws[-profile]` and github[-audience]`. Optionally for the AWS provider a duration'
-         'in seconds can be provided via `aws[-profile]_durationseconds` after which point the auto-generated'
+         'Valid values are `aws[-profile]`, `github[-audience], and `bitbucket`. Optionally for the AWS provider a '
+         'duration in seconds can be provided via `aws[-profile]_durationseconds` after which point the auto-generated'
          'credentials will expire.',
     default=None,
     show_default=True