LabVIEW gRPC Release Packages in VIPM

[KarthikAbiram]

As per quick start, there are 3 packages required, which are available in releases.

1. ni_lib_labview_grpc_library-x.x.x.x.vip
2. ni_lib_labview_grpc_servicer-x.x.x.x.vip
3. ni_lib_grpc_server_and_client_template[2]-x.x.x.x.vip

Among these 3 packages, only the 1st two packages are available in VIPM, while the 3rd one doesn't seem to be available. The 1st two packages in VIPM are also of older version (1.3.0.1) and not the latest version in releases (1.5.1.1).

If possible, it would be helpful to upload all the latest releases to VIPM.

AB#3134304

[Sacheta-NI]

Hey @KarthikAbiram , you can follow the steps in this document: https://github.com/ni/grpc-labview/blob/master/docs/QuickStart.md . Please let me know once you are able to install.

[KarthikAbiram]

I apologize, I should have better conveyed my request - I don't have issues with installing the latest version of gRPC packages from github. My request is, if we can upload the latest version of packages to VIPM as well, when the releases are uploaded to github.

Reason for the request - I am building a package on top of gRPC and give it to users. If the latest version of gRPC packages are available in VIPM, it would be easy for me to distribute my package with grpc packages as dependencies (the older version of gRPC packages in VIPM are not compatible with a gRPC service built with the latest version of packages from github releases & hence I would need to ask my users to manually install the dependent 3 packages).

[jasonmreding]

Unfortunately, the publishing to VIPM isn't something that is automated and from my understanding of things cannot be since there is no public API I could find. It is also tied to a single user account through their website so it is difficult for any maintainer to just publish a release or use an auth token or something like that. If somebody knows differently or has ideas on how to automate this so it can be done from a github action that is part of this repo, please let me know.

Because of this, we often do releases from the repo that aren't published to the VIPM community web site immediately. Instead, those are done closer to a quarterly cadence by default or on demand if somebody really needs something sooner. I don't know why two of the packages were published to VIPM and the third one wasn't. I'm guessing it was because the generator package isn't something that deploys to vilib, and it wasn't really designed to be called from user code. With that said, it would still be nice to be able to install via the community web site without having to explicitly download it from a release attached to this repo.

[KarthikAbiram]

There is a VIPM API called 'Publish VI Packages to Repository.vi' but I am unsure if its only for private repositories or for the public repository as well.

I will try checking with Jim Kring/JKI.

[KarthikAbiram]

Update from Jim: Hi Karthik. I will pass this idea along to our team for consideration. There is currently no official way to do it, but it’s worth looking into how we could support it.

[Sacheta-NI]

Hey @KarthikAbiram ,
We might take this up as feature later on when the API might be available.