APIv2 - copyViewToOtherDomains
Hello,
We are using the workflow "copyViewToOtherDomains " and discovered a few weeks ago some components will be deprecated and not replaced - private APIs “View Component” if I understood well.
What has been planned, in the next release, to offset this situation and let us still use this workflow?
Thank you in advance,
IA
Former User
Posted 5 years ago · Edited 1 year ago·Last reply 5 years ago
8 comments
Former User
OP5 years ago · EditedDear Imène,
The "copyViewToOtherDomains " workflow makes use of an API that we have flagged as deprecated. This is an indication that the View Component API is going to be removed.
We’re in a transition where we are replacing our old API with new ones. The View Component API will be dropped but not before we’ve released a new version. We want to introduce a new API that will allow you to copy views from one domain to another, like the workflow does today.
For now you can continue using the workflow and the View Component API.
We do NOT recommend making use of the graphql API as this is our internal API and it can change with every release.
Kind regards,
Kristof De Bruyne (Collibra product management)
Former User
OP5 years ago · EditedDear Kristof,
This is good news.
Thank you for the clarification.
Kind regards,
Imène AGAR
Former User
OP5 years ago · EditedHi Imene,
I spoke with our product team and it seems the APIs required for your workflow do not have an alternative yet and will remain useable until one is available. Also, we strongly discourage anyone to use the GraphQL API which is private and can break or be blocked at any time. I hope that helps.
-Bridget, Collibra Team
Former User
OP5 years ago · EditedOk, I didn’t think about graphql API. It is a potential solution to explore, thanks.
Imène
arthurburkhardt
·5 years ago · EditedIndeed… It looks like there isn’t any equivalent in either the java API or rest API.
As per documentation (https://community.collibra.com/docs/admin/5.7/#API/co_deprecated-apiv1.htm), you should open a support ticket, use the ideation forum or reach out to your CAM.
In the meantime, there are unsupported ways to achieve this, using either the migration feature with cma archives (you need to reverse engineer the validation hash, but it’s not difficult) or the graphql API.
Former User
OP5 years ago · EditedHi Arthur, restating the obvious, migration-importing a CMA file that is not directly produced by migration-export is not supported and potentially dangerous. There is a risk to corrupt the target repository beyond repair. This is why there is a hash on CMA files in the first place.
Former User
OP5 years ago · EditedHello Arthur,
Thank you for your return.
However, we already run CLI commands and we have found the workflow OOTB "copyViewToOtherDomains " uses private APIs and it does not propose an alternative solution.
Do you have recommendations to offset this situation?
See the results of the cmd below.
arthurburkhardt
·5 years ago · EditedWas this one of the workflows from the community marketplace using APIv1?
I guess the easiest is to upgrade the workflow. You can use the workflow cli solution to identify what parts of the workflow will be deprecated.
https://community.collibra.com/downloads/#cli