Replies: 2 comments
-
|
Agree that it would be more convenient to not have to lookup the guid. In the interim, here's what I've been doing to get the guid without having to launch another tool...
At the prompt, type:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm wondering why Could this not be enhanced to allow new plugins/plugin packages to be registered too (by making Furthermore could we get also additional commands to also manage (including all possible operations(eg. Create/Update/Delete/Disable/Enable) plugin steps, images, service endpoints, webhooks, custom APIs, data providers etc. Apologies for hijacking the request :) |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
We can update a plugin package via
However we have to find the GUID via the Plugin Registration Tool (
pac tool prt), see screenshot below:It would be more user-friendly to be able to specify the unique name. i.e. something similar to below.
pac plugin push --pluginid xxx_PluginsNote: The xxx_Plugins just an example name.
Beta Was this translation helpful? Give feedback.
All reactions