agilicus 1.281.0__py3-none-any.whl → 1.281.2__py3-none-any.whl

agilicus/agilicus_api/test/test_web_auth_n_enrollment_spec.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_web_auth_n_enrollment_status.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_well_known_issuer_info.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_whoami_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_whoami_request.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_whoami_response.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_workload_configuration.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_x509_certificate.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_x509_certificate_spec.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_x509_certificate_status.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_x509_root_certificate.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_x509_root_certificate_spec.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_x509_root_certificate_status.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/test/test_xss_settings.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.02.24
+    The version of the OpenAPI document: 2025.02.27
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api_README.md

@@ -3,8 +3,8 @@ Agilicus is API-first. Modern software is controlled by other software, is open,
 
 The `agilicus_api` package is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: 2025.02.24
-- Package version: 1.281.0
+- API version: 2025.02.27
+- Package version: 1.281.2
 - Build package: org.openapitools.codegen.languages.PythonClientCodegen
 For more information, please visit [https://www.agilicus.com/api](https://www.agilicus.com/api)
 
@@ -663,14 +663,20 @@ Class | Method | HTTP request | Description
 *PolicyConfigApi* | [**get_resource_url_bundle**](agilicus_api/docs/PolicyConfigApi.md#get_resource_url_bundle) | **GET** /v1/policy_config/resource_url_bundle | Get the global resource url bundle
 *RegionsApi* | [**add_cluster**](agilicus_api/docs/RegionsApi.md#add_cluster) | **POST** /v1/clusters | Add a Cluster
 *RegionsApi* | [**add_point_of_presence**](agilicus_api/docs/RegionsApi.md#add_point_of_presence) | **POST** /v1/point_of_presences | Add a point of presence.
+*RegionsApi* | [**add_region**](agilicus_api/docs/RegionsApi.md#add_region) | **POST** /v1/regions | Add a Region
 *RegionsApi* | [**delete_cluster**](agilicus_api/docs/RegionsApi.md#delete_cluster) | **DELETE** /v1/clusters/{cluster_id} | Delete a Cluster
 *RegionsApi* | [**delete_point_of_presence**](agilicus_api/docs/RegionsApi.md#delete_point_of_presence) | **DELETE** /v1/point_of_presences/{point_of_presence_id} | Delete a point of presence
+*RegionsApi* | [**delete_region**](agilicus_api/docs/RegionsApi.md#delete_region) | **DELETE** /v1/regions/{region_id} | Delete a Region
 *RegionsApi* | [**get_cluster**](agilicus_api/docs/RegionsApi.md#get_cluster) | **GET** /v1/clusters/{cluster_id} | Get a Cluster
 *RegionsApi* | [**get_point_of_presence**](agilicus_api/docs/RegionsApi.md#get_point_of_presence) | **GET** /v1/point_of_presences/{point_of_presence_id} | Get a point of presence
+*RegionsApi* | [**get_region**](agilicus_api/docs/RegionsApi.md#get_region) | **GET** /v1/regions/{region_id} | Get a Region
 *RegionsApi* | [**list_clusters**](agilicus_api/docs/RegionsApi.md#list_clusters) | **GET** /v1/clusters | List all Clusters
 *RegionsApi* | [**list_point_of_presences**](agilicus_api/docs/RegionsApi.md#list_point_of_presences) | **GET** /v1/point_of_presences | List all regions
+*RegionsApi* | [**list_regions**](agilicus_api/docs/RegionsApi.md#list_regions) | **GET** /v1/regions | List all regions
 *RegionsApi* | [**replace_cluster**](agilicus_api/docs/RegionsApi.md#replace_cluster) | **PUT** /v1/clusters/{cluster_id} | update a Cluster
 *RegionsApi* | [**replace_point_of_presence**](agilicus_api/docs/RegionsApi.md#replace_point_of_presence) | **PUT** /v1/point_of_presences/{point_of_presence_id} | update a point of presence
+*RegionsApi* | [**replace_region**](agilicus_api/docs/RegionsApi.md#replace_region) | **PUT** /v1/regions/{region_id} | update a Region
+*RegionsApi* | [**routing_request**](agilicus_api/docs/RegionsApi.md#routing_request) | **POST** /v1/routing_request | Request routing
 *ResourcesApi* | [**add_resource**](agilicus_api/docs/ResourcesApi.md#add_resource) | **POST** /v1/resources | Add a resource
 *ResourcesApi* | [**delete_resource**](agilicus_api/docs/ResourcesApi.md#delete_resource) | **DELETE** /v1/resources/{resource_id} | Delete a resource
 *ResourcesApi* | [**get_resource**](agilicus_api/docs/ResourcesApi.md#get_resource) | **GET** /v1/resources/{resource_id} | Get a resource
@@ -763,7 +769,7 @@ Class | Method | HTTP request | Description
 *UsersApi* | [**bulk_update_metadata**](agilicus_api/docs/UsersApi.md#bulk_update_metadata) | **POST** /v1/user_metadata_rpc/bulk_update | Update a group of user's metadata for the specified org
 *UsersApi* | [**create_challenge_method**](agilicus_api/docs/UsersApi.md#create_challenge_method) | **POST** /users/{user_id}/mfa_challenge_methods | Create a multi-factor authentication method
 *UsersApi* | [**create_service_account**](agilicus_api/docs/UsersApi.md#create_service_account) | **POST** /v1/service_accounts | Create a service account
-*UsersApi* | [**create_suppport_user**](agilicus_api/docs/UsersApi.md#create_suppport_user) | **POST** /v1/support_users | Create a support user
+*UsersApi* | [**create_support_user**](agilicus_api/docs/UsersApi.md#create_support_user) | **POST** /v1/support_users | Create a support user
 *UsersApi* | [**create_upstream_user_identity**](agilicus_api/docs/UsersApi.md#create_upstream_user_identity) | **POST** /users/{user_id}/upstream_user_identities | Create an upstream user identity
 *UsersApi* | [**create_user**](agilicus_api/docs/UsersApi.md#create_user) | **POST** /users | Create a user
 *UsersApi* | [**create_user_identity_update**](agilicus_api/docs/UsersApi.md#create_user_identity_update) | **POST** /users/{user_id}/user_identity_updates | Update a user's core identity information.
@@ -771,14 +777,14 @@ Class | Method | HTTP request | Description
 *UsersApi* | [**create_user_request**](agilicus_api/docs/UsersApi.md#create_user_request) | **POST** /v1/user_requests | Create a request on behalf of the user
 *UsersApi* | [**delete_challenge_method**](agilicus_api/docs/UsersApi.md#delete_challenge_method) | **DELETE** /users/{user_id}/mfa_challenge_methods/{challenge_method_id} | Delete a user's multi-factor authentication challenge method
 *UsersApi* | [**delete_service_account**](agilicus_api/docs/UsersApi.md#delete_service_account) | **DELETE** /v1/service_accounts/{service_account_id} | Delete a service account
-*UsersApi* | [**delete_support_user**](agilicus_api/docs/UsersApi.md#delete_support_user) | **DELETE** /v1/support_users/{user_id} | Delete a support user
+*UsersApi* | [**delete_support_user**](agilicus_api/docs/UsersApi.md#delete_support_user) | **DELETE** /v1/support_users/{support_user_id} | Delete a support user
 *UsersApi* | [**delete_upstream_user_identity**](agilicus_api/docs/UsersApi.md#delete_upstream_user_identity) | **DELETE** /users/{user_id}/upstream_user_identities/{upstream_user_identity_id} | Delete an upstream user identity
 *UsersApi* | [**delete_user**](agilicus_api/docs/UsersApi.md#delete_user) | **DELETE** /v1/orgs/{org_id}/users/{user_id} | Remove a user from an organisation
 *UsersApi* | [**delete_user_metadata**](agilicus_api/docs/UsersApi.md#delete_user_metadata) | **DELETE** /v1/user_metadata/{metadata_id} | Delete an user metadata entry
 *UsersApi* | [**delete_user_request**](agilicus_api/docs/UsersApi.md#delete_user_request) | **DELETE** /v1/user_requests/{user_request_id} | Delete an user request
 *UsersApi* | [**get_challenge_method**](agilicus_api/docs/UsersApi.md#get_challenge_method) | **GET** /users/{user_id}/mfa_challenge_methods/{challenge_method_id} | Get a single challenge method for the given user
 *UsersApi* | [**get_service_account**](agilicus_api/docs/UsersApi.md#get_service_account) | **GET** /v1/service_accounts/{service_account_id} | Get a service account
-*UsersApi* | [**get_support_user**](agilicus_api/docs/UsersApi.md#get_support_user) | **GET** /v1/support_users/{user_id} | Get a support user
+*UsersApi* | [**get_support_user**](agilicus_api/docs/UsersApi.md#get_support_user) | **GET** /v1/support_users/{support_user_id} | Get a support user
 *UsersApi* | [**get_upstream_user_identity**](agilicus_api/docs/UsersApi.md#get_upstream_user_identity) | **GET** /users/{user_id}/upstream_user_identities/{upstream_user_identity_id} | Get a single upstream user identity
 *UsersApi* | [**get_user**](agilicus_api/docs/UsersApi.md#get_user) | **GET** /users/{user_id} | Get a single user
 *UsersApi* | [**get_user_metadata**](agilicus_api/docs/UsersApi.md#get_user_metadata) | **GET** /v1/user_metadata/{metadata_id} | Get a single user metadata entry
@@ -814,7 +820,7 @@ Class | Method | HTTP request | Description
 *UsersApi* | [**replace_user_role**](agilicus_api/docs/UsersApi.md#replace_user_role) | **PUT** /users/{user_id}/roles | Create or update a user role
 *UsersApi* | [**reset_user_identity**](agilicus_api/docs/UsersApi.md#reset_user_identity) | **POST** /users/{user_id}/reset_user_identity | Resets a user's identity if allowed
 *UsersApi* | [**reset_user_mfa_challenge_methods**](agilicus_api/docs/UsersApi.md#reset_user_mfa_challenge_methods) | **POST** /users/{user_id}/reset_mfa_challenge_methods | Resets a user's multi-factor authentication method
-*UsersApi* | [**update_support_user**](agilicus_api/docs/UsersApi.md#update_support_user) | **PUT** /v1/support_users/{user_id} | Update a support user's expiry
+*UsersApi* | [**update_support_user**](agilicus_api/docs/UsersApi.md#update_support_user) | **PUT** /v1/support_users/{support_user_id} | Update a support user's expiry
 *UsersApi* | [**update_user_request**](agilicus_api/docs/UsersApi.md#update_user_request) | **POST** /v1/user_requests/{user_request_id} | Uses the state parameter in the body to apply the action to the request
 *WhoamiApi* | [**create_whoami**](agilicus_api/docs/WhoamiApi.md#create_whoami) | **POST** /v1/whoami | login through whoami
 
@@ -1233,6 +1239,7 @@ Class | Method | HTTP request | Description
  - [ListPolicyTemplateInstancesResponse](agilicus_api/docs/ListPolicyTemplateInstancesResponse.md)
  - [ListProductsResponse](agilicus_api/docs/ListProductsResponse.md)
  - [ListPublicFileOrgLinksResponse](agilicus_api/docs/ListPublicFileOrgLinksResponse.md)
+ - [ListRegionResponse](agilicus_api/docs/ListRegionResponse.md)
  - [ListResourceGroupsResponse](agilicus_api/docs/ListResourceGroupsResponse.md)
  - [ListResourcePermissionsResponse](agilicus_api/docs/ListResourcePermissionsResponse.md)
  - [ListResourceRolesResponse](agilicus_api/docs/ListResourceRolesResponse.md)
@@ -1412,6 +1419,10 @@ Class | Method | HTTP request | Description
  - [ReconcileSubOrgIssuerRequest](agilicus_api/docs/ReconcileSubOrgIssuerRequest.md)
  - [ReferrerPolicySettings](agilicus_api/docs/ReferrerPolicySettings.md)
  - [RefreshTokenRequest](agilicus_api/docs/RefreshTokenRequest.md)
+ - [Region](agilicus_api/docs/Region.md)
+ - [RegionRouting](agilicus_api/docs/RegionRouting.md)
+ - [RegionSpec](agilicus_api/docs/RegionSpec.md)
+ - [RegionStatus](agilicus_api/docs/RegionStatus.md)
  - [RemoteAppAccessInfo](agilicus_api/docs/RemoteAppAccessInfo.md)
  - [RenderedQueryParameter](agilicus_api/docs/RenderedQueryParameter.md)
  - [RenderedResourcePermissions](agilicus_api/docs/RenderedResourcePermissions.md)
@@ -1449,6 +1460,7 @@ Class | Method | HTTP request | Description
  - [RoleV2](agilicus_api/docs/RoleV2.md)
  - [Roles](agilicus_api/docs/Roles.md)
  - [RolesConfig](agilicus_api/docs/RolesConfig.md)
+ - [RoutingRequest](agilicus_api/docs/RoutingRequest.md)
  - [Rule](agilicus_api/docs/Rule.md)
  - [RuleAction](agilicus_api/docs/RuleAction.md)
  - [RuleCondition](agilicus_api/docs/RuleCondition.md)

agilicus/connectors.py

@@ -230,6 +230,12 @@ def format_connectors_as_text(
     columns = [
         metadata_column("id"),
         spec_column("name"),
+        column(
+            "stats",
+            newname="last_status_change",
+            getter=_get_oper_status_change,
+            optional=True,
+        ),
     ]
     if "metadata.created" in sort_by:
         columns.append(metadata_column("created"))

agilicus/issuers.py

@@ -1398,3 +1398,24 @@ def format_policy_table_joined(ctx, policy: agilicus.PolicySpec):
 
     data = groups_from_api(policy)
     return format_table(ctx, data, columns)
+
+
+def add_fake_upstream(ctx, issuer_id, **kwargs):
+    return add_oidc_upstreams(
+        ctx,
+        issuer_id,
+        "fake-oidc",
+        "fake-oidc",
+        "https://fake-oidc-server.local.agilicus.dev",
+        "lms",
+        "fos-secret",
+        None,
+        None,
+        None,
+        None,
+        False,
+        True,
+        None,
+        "oidc",
+        **kwargs,
+    )

agilicus/main.py

@@ -1142,6 +1142,7 @@ def create_portal_link(ctx, **kwargs):
 @click.option("--shard", default=None)
 @click.option("--disable-user-requests", type=bool, default=None)
 @click.option("--ruleset-bundle-id", default=None)
+@click.option("--region-id", default=None)
 @click.pass_context
 def update_org(
     ctx,
@@ -7931,6 +7932,11 @@ def add_point_of_presence(ctx, **kwargs):
 @click.option("--master-cluster-id", default=None)
 @click.option("--add-cluster-id", multiple=True)
 @click.option("--remove-cluster-id", multiple=True)
+@click.option("--org-domain", multiple=True)
+@click.option("--public", type=bool, default=None)
+@click.option("--restrict-by-user-id", type=bool, default=None)
+@click.option("--add-permitted-user-id", multiple=True)
+@click.option("--remove-permitted-user-id", multiple=True)
 @click.option(
     "--overwrite-tags",
     is_flag=True,
@@ -7941,6 +7947,7 @@ def add_point_of_presence(ctx, **kwargs):
     is_flag=True,
     help="overwrites the domains rather than adding to them",
 )
+@click.option("--requests-enabled", type=bool, default=None)
 @click.pass_context
 def update_point_of_presence(
     ctx, point_of_presence_id, add_cluster_id, remove_cluster_id, **kwargs
@@ -8024,6 +8031,88 @@ def update_cluster(ctx, add_ip_address, remove_ip_address, *args, **kwargs):
     )
 
 
+@cli.command(name="list-regions")
+@click.option("--limit", default=500)
+@click.pass_context
+def list_regions(ctx, **kwargs):
+    results = regions.list_regions(ctx, **kwargs)
+    columns = make_columns(
+        ctx,
+        results,
+        """
+          - metadata.id(newname=id)
+          - spec.name(newname=name)
+          - spec.master_pop_id(newname=master)
+          - spec.routing(newname=routing)
+          - status.pops:
+            - metadata.id(newname=id)
+            - spec.name(newname=name)
+            - spec.routing(newname=routing)
+        """,
+    )
+    print(format_table(ctx, results, columns))
+
+
+@cli.command(name="add-region")
+@click.argument("name")
+@click.option("--domain", multiple=True)
+@click.pass_context
+def add_region(ctx, **kwargs):
+    result = regions.add_region(ctx, **kwargs)
+    output_entry(ctx, result.to_dict())
+
+
+@cli.command(name="update-region")
+@click.argument("region-id")
+@click.option("--name", default=None)
+@click.option("--domain", multiple=True)
+@click.option("--org-domain", multiple=True)
+@click.option("--master-pop-id", default=None)
+@click.option("--add-pop-id", multiple=True)
+@click.option("--remove-pop-id", multiple=True)
+@click.option("--requests-enabled", type=bool, default=None)
+@click.option("--public", type=bool, default=None)
+@click.option("--restrict-by-user-id", type=bool, default=None)
+@click.option("--add-permitted-user-id", multiple=True)
+@click.option("--remove-permitted-user-id", multiple=True)
+@click.option(
+    "--overwrite-domains",
+    is_flag=True,
+    help="overwrites the domains rather than adding to them",
+)
+@click.pass_context
+def update_region(ctx, region_id, add_pop_id, remove_pop_id, **kwargs):
+    result = regions.update_region(
+        ctx,
+        region_id=region_id,
+        add_pop_ids=list(add_pop_id),
+        remove_pop_ids=list(remove_pop_id),
+        **kwargs,
+    )
+    output_entry(ctx, result.to_dict())
+
+
+@cli.command(name="delete-region")
+@click.argument("region_id")
+@click.pass_context
+def delete_region(ctx, *args, **kwargs):
+    regions.delete_region(ctx, *args, **kwargs)
+
+
+@cli.command(name="routing-request")
+@click.option("--ip_address")
+@click.pass_context
+def routing_request(ctx, *args, **kwargs):
+    output_entry(ctx, regions.routing_request(ctx, *args, **kwargs).to_dict())
+
+
+@cli.command(name="build-agilicus-locations")
+@click.option("--fail-on-domain-lookup-failure", default=True)
+@click.pass_context
+def build_agilicus_locations(ctx, *args, **kwargs):
+    regions.build_agilicus_locations(ctx, *args, **kwargs)
+
+
 @cli.command(name="list-connector-queues")
 @click.option("--org-id", default=None)
 @click.option("--connector-id", default=None)
@@ -8450,6 +8539,15 @@ def delete_connector_services(ctx, *args, **kwargs):
     connectors.delete_service(ctx, *args, **kwargs)
 
 
+@cli.command(name="add-fake-oidc-issuer")
+@click.argument("issuer-id")
+@click.option("--org-id", default=None)
+@click.pass_context
+def add_fake_oidc_issuer(ctx, *args, **kwargs):
+    result = issuers.add_fake_upstream(ctx, *args, **kwargs)
+    output_entry(ctx, result)
+
+
 def main():
     trusted_certs_main.add_commands(cli)
     hosts_main.add_commands(cli)

agilicus/orgs.py

@@ -137,6 +137,7 @@ def update(  # noqa: max-complexity: 19
     cluster=None,
     ruleset_bundle_id=None,
     point_of_presence_id=None,
+    region_id=None,
 ):
     token = context.get_token(ctx)
 
@@ -202,6 +203,9 @@ def update(  # noqa: max-complexity: 19
     if point_of_presence_id is not None:
         data["point_of_presence_id"] = point_of_presence_id
 
+    if region_id is not None:
+        data["region_id"] = region_id
+
     for i in list(data):
         if data[i] is None:
             del data[i]