v2.1.0-rc.1

CHANGELOG.md

@@ -3,6 +3,28 @@
 > As of v1.4.0, release candidates will be published in an effort to get new features out faster while still allowing
 > time for full QA testing before moving the release candidate to a full release.
 
+## v2.1.0-rc.1 [2025-02-24]
+
+__What's New:__
+
+* None
+
+__Enhancements:__
+
+* None
+
+__Bug Fixes:__
+
+* None
+
+__Dependencies:__
+
+* `colored>=2.2.5`
+
+__Other:__
+
+* Tests and Documentation updates for SDK alignment.
+
 ## v2.1.0-rc.0 [2025-01-27]
 
 __What's New:__

docs/index.md

@@ -180,7 +180,7 @@ Below is the list of application types in which a 2 part format is acceptable.
 The list can be generated (assuming the caller has the required permissions) on demand with the following command.
 
 ```sh
-pybritive api applications.catalog \
+pybritive api application_management.applications.catalog \
     --query '[*].{"application type": name,"2 part format allowed":requiresHierarchicalModel}' \
     --format table
 ```
@@ -403,16 +403,16 @@ Usage examples of: (`pybritive api method --parameter1 value1 --parameter2 value
 
 ```sh
 # list all users in the britive tenant
-pybritive api users.list
+pybritive api identity_management.users.list
 
 # create a tag
-pybritive api tags.create --name testtag --description "test tag"
+pybritive api identity_management.tags.create --name testtag --description "test tag"
 
 # list all users and output just the email address of each user via jmespath query
-pybritive api users.list --query '[].email'
+pybritive api identity_management.users.list --query '[].email'
 
 # create a profile
-pybritive api profiles.create --application-id <id> --name testprofile
+pybritive api application_management.profiles.create --application-id <id> --name testprofile
 
 # create a secret
 pybritive api secrets_manager.secrets.create --name test --vault-id <id> --value '{"Note": {"secret1": "abc"}}'

pyproject.toml

@@ -28,7 +28,7 @@ requires-python = ">= 3.9"
 dependencies = [
     "britive~=4.0",
     "click>=8.1.7",
-    "colored",
+    "colored>=2.2.5",
     "cryptography",
     "jmespath",
     "merge-args",

requirements.txt

@@ -4,7 +4,7 @@ britive~=4.0
 certifi
 charset-normalizer
 click>=8.1.7
-colored
+colored>=2.2.5
 cryptography
 google-cloud-compute
 jmespath

src/pybritive/__init__.py

@@ -1 +1 @@
-__version__ = '2.1.0-rc.0'
+__version__ = '2.1.0-rc.1'

src/pybritive/commands/api.py

@@ -33,13 +33,13 @@ def api(ctx, query, output_format, tenant, token, silent, passphrase, federation
 
     * generic: pybritive api method --parameter1 value1 --parameter2 value2 [--parameterX valueX]
 
-    * pybritive api users.list
+    * pybritive api identity_management.users.list
 
-    * pybritive api tags.create --name testtag --description "test tag"
+    * pybritive api identity_management.tags.create --name testtag --description "test tag"
 
-    * pybritive api users.list --query '[].email'
+    * pybritive api identity_management.users.list --query '[].email'
 
-    * pybritive api profiles.create --application-id <id> --name testprofile
+    * pybritive api application_management.profiles.create --application-id <id> --name testprofile
 
     """
     parameters = {ctx.args[i][2:]: ctx.args[i + 1] for i in range(0, len(ctx.args), 2)}

tests/test_0500_api.py

@@ -7,5 +7,5 @@ def common_asserts(result, substring=None, exit_code=0):
 
 
 def test_api(runner, cli):
-    result = runner.invoke(cli, 'api users.list'.split(' '))
+    result = runner.invoke(cli, 'api identity_management.users.list'.split(' '))
     common_asserts(result, ['userId', 'status', 'email', 'identityProvider'])