-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/v12 #1000
Feature/v12 #1000
Conversation
@rclapp, @janus-t, @Wuzardor, This Pull Request contains all commits from Ryan's branch but is rebased on the current master and contains one additional commit to adapt the branch for PAaaS: 608cdca Above is an example of how you can use the branch with PAaaS in the IBM Cloud. @rclapp I limited my changes to the I introduced an enum in the Now I will do more testing and try to make things pretty and name things more appropriately. |
Hi everyone, Marius, thank you for your work. I don't know how to test the code you've developed in the branch 608cdca to check the TM1py connection for PAaaS. Regarding the question about the tenant, here is a brief explanation: In the context of IBM services, "tenant" typically refers to a specific instance or client of a cloud service. Each client is considered a distinct "tenant" with isolated resources and configurations. When connecting to an IBM service, the URL may include a reference to the tenant, directing authentication and authorization to the specific instance you want to access. For example, in the URL "https://service.ibm.com/tenant1234/resource," "tenant1234" is the tenant identifier. The service uses this information to ensure access to the appropriate resources within that specific tenant. |
Thanks for the background on the tenant vs instance concepts. You can upgrade your local TM1py to this branch with the pip statement below.
Then you can test it easily if you have access to a v12 instance. from TM1py import TM1Service
with TM1Service(
address="us-east-2.aws.planninganalytics.ibm.com",
api_key="AB4VfG7T8wPM-912uFKeYG5PGh0XbS80MVBAt7SEG6xn",
iam_url="https://iam.cloud.ibm.com/identity/token",
tenant="YA9A2T8BS2ZU",
database="CWRecordsMDX") as tm1:
print(tm1.dimensions.get_all_names()) |
17b6019
to
18ca7ba
Compare
* Moved api path to base url to continue to support v11 * Refactored all services to continue v11 support and expand support to v12 using the base_url property. * Update config.ini Fixed test fixture config * Corrected test_get_threads to include api/v1 in the path * Support for v12 Auth with backwards compatibility. * Updates to cell service to support v12 using blobs. Updates include tests, new utils for skipping invalid tests, and updates to the FileService.py * Updates to services and tests to support v12 * Updates to services and tests to support v12 * Small change to CubeService_test.py to use a real rule statement in the get all names test. Test used to use comments which seem unreliable across versions. * Updates to the ProcessService and HierarchyService and related tests. * Removed test that requires control process, not all models have control processes. * New functions request the server metadata and update system logger levels * Updates to process tests * Remove ODATA tags that are not needed * Updates to the application service to support v12. Updated tests to resolve dependency issues with chores and processes. * New manage service that allows you to control the PAe control plane * Remove support for Impersonation and ErrorLogs entity * Manage Service Updates * Manage Service Updates and small fixes to security tests * Simplification of the auth and root creation methods
prototype return_async_id feature
a342b06
to
f49ae3c
Compare
rebased on current master and ready to be merged IMO |
30dddc2
to
91d0af0
Compare
v12 feature branch based on https://github.com/rclapp/TM1py/tree/tm1-v12-ga-release-testing
Adapted to work with TM1 v12 in IBM Cloud (PaaS).