Does Publishing a New Version of an Action Automatically Update It in All Workflows in Pipedream?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi Pipedream team,

My company is looking to develop private components for re-use across workflows, likely both sources and actions. I’d like to understand better the lifecycle of those components. For example, when we publish a new version of an action, will that update automatically propagate to any of our workflows using that action?

2

And if updates don’t automatically propagate, what is the best way to orchestrate a process to do that for us?

3

Components are not automatically updated, no. You need to update the components in the workflow builder and redeploy the workflow.

I don’t think there is a programmatic way to update components within workflows.

4

Thanks ! A couple of other questions:

So if we have a private component we’ve used across 10 different workflows, is there anyway to know which which is using that component?

The public Components in your Github repo use the defineApp(...) function, but this isn’t documented anywhere. Does it make sense for private Components to use this as well? Is there any documentation for how to use defineApp?

Both of your Github workflows for components appear to skip the .app.{ts,js} files when publishing. Why is this? It looks like those files contain reusable prop and method definitions, how do that work if those files are published too?

5

You only need the define functions if using Typescript, otherwise you can just export the object directly - most registry components do the latter

6

Typescript files are first compiled into .mjs files before being published. More info here: TypeScript Components - Pipedream

7

And components are published along with their dependencies - usually they’re .mjs files though, not .js

8

Re: a private component used across 10 different workflows, I believe you have to manually update the component in each workflow when publishing a new version - I don’t think there is another way to do this

9

Thanks for all of the answers!

10

Re: a private component used across 10 different workflows, I believe you have to manually update the component in each workflow when publishing a new version - I don’t think there is another way to do this
Understood. But what I was asking was how to find all of the workflows which are using that component.