No plan to integrate LCM from Workspace Admin with the GIT feature in the Workspace Modeling Workbench. We plan to keep these as distinct features as they are commonly leveraged by different user roles.
That being said, we are thinking longer term about version control for Workspace content.
Original Message:
Sent: Thu October 12, 2023 11:16 AM
From: Ardian Alikaj
Subject: PAW Git repository integration Issues
Hi Hubert,
Today, in order to migrate PAW content, we have to use the Lifecycle Manager from PAW Administration. That process creates a compressed file with all selected objects, and then we import that file in the destination. My question was, since the GIT-IntegrationMigration for TM1 backend objects (including Websheets) is introduced in PAW, is there any plan to integrate this "lifecycle management" capability with GIT
Thank you
------------------------------
Ardian Alikaj
Original Message:
Sent: Thu October 12, 2023 10:43 AM
From: Hubert Heijkers
Subject: PAW Git repository integration Issues
Hi Ardian,
Not sure what you mean by a 'GIT deployment packages' but I if you are asking if there are plans to include PAW contents in source for a TM1 database I'd expect the answer would be no, that seems unlikely, but more a question for Stuart.
Are you looking for a GIT based 'solution' for a complete PA[W] deployment??? Which presumably could contain multiple TM1 databases, and containing contents that might be sourced from those TM1 databases as well as external sourced?
------------------------------
Hubert Heijkers
STSM, Program Director TM1 Functional Database Technology and OData Evangelist
Original Message:
Sent: Thu October 12, 2023 10:10 AM
From: Ardian Alikaj
Subject: PAW Git repository integration Issues
Hi Hubert,
Is there any plan to include the PAW Content (Books, Dashboards etc) in GIT deployment packages (at least Book Specifications)?
Thanks
------------------------------
Ardian Alikaj
Original Message:
Sent: Thu October 12, 2023 08:42 AM
From: Hubert Heijkers
Subject: PAW Git repository integration Issues
Great to see Planning Analytics starting to take full advantage of the GIT integration functionality provided by TM1 (a.k.a. PAE), love it!
Just wanted to add thought that, whilst people seem to be looking for capabilities to simply 'move objects across', the GIT integration functionality was designed for scenarios where you'd not be storing the materialized database but rather the source of such database.
Whilst a replication scenario can be described as source, as Stuart shows in the above demo, there are many more scenarios that that could written up that source from other places, as you normally would already, and code this up in the source to allow for automation of deployment/standing up such database from scratch.
Another part of that is the notion of deployment environments (deployments) which allows developers to individual specify things like the security used in dev vs. test and production , which data is get loaded in each of these environments or even what objects to be deployed or not for example. Trust that PA, now that files are tackled, will add support for different deployments as well at some point in the future Stuart?
PS Noticed a comment above wrt not removing objects. That was a deliberate choose when we designed and implemented the GIT integration some 5-6 years ago to allow for objects to exist, like the Bedrock library, without having to be part of the source itself. Given that mature database typically don't change as much one could add a post-pull task to clear any evidence of past versions to coupe with situations where things should be removed.
------------------------------
Hubert Heijkers
STSM, Program Director TM1 Functional Database Technology and OData Evangelist
Original Message:
Sent: Wed October 11, 2023 08:25 PM
From: STUART KING
Subject: PAW Git repository integration Issues
FYI...
------------------------------
Stuart King
IBM Planning Analytics Offering Manager
Original Message:
Sent: Tue October 10, 2023 12:35 AM
From: Karl Blackler
Subject: PAW Git repository integration Issues
Hi Vedrana,
Our initial review of the Git integration left us feeling underwhelmed, there were many missing object types.
I didn't notice the tm1project.json file, I might review this again to see if some of the missing control objects can be added in.
This was our assessment;
| Git Hub Integration with IBM Planning Analytics |
| Cubes | | |
| | Cube Security | No | }CubeSecurity |
| | Data | No | |
| | Dimension List | Yes | |
| | Rules | Yes | |
| | Views | Yes | |
| Dimensions | | |
| | Attributes | No | }ElementAttributes |
| | Dimension Security | No | }DimensionSecurity |
| | Element Security | No | }ElementSecurity |
| | Elements | Yes | |
| | Hierarchies | Yes | |
| | Subsets | Yes | |
| Processes | | |
| | Code | Yes | |
| | Process Security | No | }ProcessSecurity |
| Chores | | |
| | Chore Security | No | }ChoreSecurity |
| | Processes | Yes | |
| | Time | Yes | |
| | | | |
| Control Objects | | |
| | Only } items that can be included is non-system items. | | |
| | No }ElementAttribute | No | |
| | No }ElementSecurity | No | |
| | No }cubeSecurity | No | |
| | | | |
| | Only | | |
| | }Drill processes | Yes | |
| | user defined } dims/cubes | Yes | |
I also hoped to add additional files, like csv or txt files, readme files, etc.
We've started looking at the REST API to perform some of the replication type functions.
Stuart King gives a good demo here;
Lets hope we see some updates to the Integration soon.
Thanks
------------------------------
Karl Blackler
Original Message:
Sent: Mon October 09, 2023 10:54 AM
From: Vedrana Tomic
Subject: PAW Git repository integration Issues
Dear Planning Analytics Community,
I am using PAW Version 2.0.86 and tried to use the newly introduced feature to integrate Git for Planning Analytics database objects.
During that process I have noticed a couple things that I'd like to address and get your opinion on:
- tm1project.json
This file is used to decide which Objects should be included and which ignored when committing/pushing to Git. In the new Git feature, where you can select what you want to commit over the GUI, many Control Cubes aren't included and there is no way to include them other than manually editing the tm1project.json (by TM1 API) right before committing the changes. This is hacky and surely not designed to work this way. Does anyone know the background why not all objects are considered in the GUI and if they plan to change this in the future?
- Deletion/Removal of obsolete objects
When pulling from a Branch to update my current model, objects that do not exist in the repository anymore are not being deleted in the model. Only changes and newly added objects are reflected in the model, which means that I still need to manually write down all the objects that I want to delete, then remove them manually. Any ideas how to accommodate this issue or if this will be improved in the future?
- Author
This might be an Azure DevOps-specific issue, but since I log in with an "admin" account to PAW and make my commits from that account, in DevOps the Author is simply displayed as "Admin" and doesn't provide the required information of who actually made the changes. Even though I provide an Azure E-Mail Address when prompted, but it's being ignored. Does anyone have any experience on this? I have not been able to find any info online.
Generally, I am missing a lot of documentation/information on how the Git integration process is supposed to work... With lots of trial and error I have now been able to make some sense of it, but it still feels very shaky.
Looking forward to hearing some inputs from the community and also those that have been using the Rest API and if you've noticed any differences.
Thank you !
------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna
------------------------------
------------------------------