NI Package Management Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
MaximeR

Add ability to add/remove a feed with a package

Status: New

Hello,

 

I want to distribute my packages with a specific feed. This can be very usefull to distribute application to customer and push updates. But if we use a specific feed, it's not straightforward. We can use the nipkg CLI command to add/remove the feed but it's not so easy to deploy to customer. It's often more easy to request IT to let NI Package Manager to have Admin right than to allow bat file for example.

 

So my idea is to give ability to install a package that also register the feed. After install the package, it can have access to updates more easily. If he uninstall the package it can interresting to unregister the feed. In this way, it can be also easy to update the feed by pushing an update of the package.

 

Note : I tried to do it with pre and post install command without success.

 

Best regards.

 

 

Maxime R.  

  CLA - Certified LabVIEW Architect / Architecte LabVIEW Certifié
  CTA - Certified TestStand Architect / Architecte TestStand Certifié

2 Comments
jyoung8711
Member

I would further add, that it would be nice to be able to create a "Add feed only" package that JUST registers feeds... Similar to how NI has the "online" exes that you can download from NI.com/downloads which only reference packages in feeds and so are very small.

 

My use case is deploying packages inside of an organization with no outward internet connections.  We can create local feeds, having an "easy" way to allow individuals to subscribe to them w/out using the NIPM advanced feed management would be incredibly useful

ChrisStrykesAgain
Active Participant

I'd also like to see the ability to remove feeds, similar to what this SystemLink state file does: https://github.com/joshuaprewitt/systemlink-state-examples/blob/master/Remove%20NIPM%20Feeds.sls

 

My specific goal is to be able to remove the ni.com NIPM feed from a minion when installing the package, but also have an uninstall action that re-adds it.

 

Currently doing this with a post-install all action seems to cause a software hang on install that requires cancelling the job (when deploying from SL) or killing the process (when using NI Package Manager natively).

--------------------------------------