The scenario you would use it is when you want to reuse your own private collection of npm registry. But first you would need to have it 🙂 Take a look at https://verdaccio.org . I believe benefits are going be similar.
That’s correct. It’s irrelevant for the worfklow to work.
I recommend to use GUI in GCP Dataform instead .yaml file to create release conf and corresponding workflow conf. Run manually first and check BQ whether tables and views have been created.
Cheers
There are two separate things:
1. [Your Title] Dataform npm package - package delivered by Dataform team and distributed through for free https://www.npmjs.com
2. [Screenshot] Npm private packages - essentially non-open-source packages which are not available to the public e.g. developed and used within your company
Is there anything specific you are trying to achieve?
Hi @caloric8585 ,
Thanks for the info. No, not specific thing to achieve. Just want to know when we should be using it and for what specific job?
The moment i'm only trying to integrate Dataform with GitHub and using Workflows to execute the pipeline. Integration between Dataform and GitHub is working well. I'm not sure if it will work with Workflows. And i guess this is nothing to do with the NPM package?
The scenario you would use it is when you want to reuse your own private collection of npm registry. But first you would need to have it 🙂 Take a look at https://verdaccio.org . I believe benefits are going be similar.
That’s correct. It’s irrelevant for the worfklow to work.
I recommend to use GUI in GCP Dataform instead .yaml file to create release conf and corresponding workflow conf. Run manually first and check BQ whether tables and views have been created.
Cheers