How to Deploy Changes to a Custom Source Without Creating a New One After Closing the Terminal?

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

i already deployed a custom source and closed the terminal , how do i deploy the changes i made to the source without creating a new one

To deploy changes to an existing custom source without creating a new one, you can use the Pipedream CLI (pd deploy) command with the same source file you initially deployed. Make sure to apply your changes to this file first. The CLI will recognize the source based on the name and key properties within your source code and update the existing source instead of creating a new one. Here’s a general example of how to deploy changes: bash pd deploy my-source.js Replace my-source.js with the filename of your source code. This command will update the existing source with any changes made in the file. For more information on deploying sources via CLI, you can refer to the Pipedream documentation on deploying components from local code.

how ot get source id

To get the ID of your source in Pipedream, you can follow these steps: 1. Visit Sign Up - Pipedream. 2. Select the source you’re interested in. 3. Copy its ID from the URL. It’s the string that starts with dc_. Alternatively, you can find the ID by using the Pipedream CLI with the command pd list sources, which will list all of your sources along with their IDs. For more details, please refer to the Pipedream documentation: REST API - Pipedream.

watch:add | C:\Users\m_his\OneDrive\Pictures\Documents\GitHub\pipedream-custom-sources-2\github-issues\github_issues.mjs
Fetching existing…
error | existing deployed component does not match
Waiting for file change (or ^C to quit)…

It seems like you’re encountering an issue with the pd dev command while working with a Pipedream custom source for GitHub issues. The error message “existing deployed component does not match” typically indicates that the local component you’re trying to update with pd dev does not match the version that’s currently deployed on Pipedream. To resolve this issue, you might want to try the following steps: 1. Ensure that you’re working on the correct version of your component. If you’ve made changes to the component on Pipedream’s UI, make sure to pull those changes to your local environment. 2. If you’re certain that you want to update the existing deployed component with your local version, you can use the --dc flag with the pd dev command to specify the deployed component ID you wish to update. You can find the deployed component ID in the URL when you view your source in the Pipedream UI. The command format should look like this: bash pd dev --dc <existing-deployed-component-id> <path-to-your-component-file> Replace <existing-deployed-component-id> with your actual deployed component ID and <path-to-your-component-file> with the path to your .mjs file. 3. If the issue persists, consider deploying a new version of your component and making sure any dependencies or changes are correctly reflected in your local file. For more detailed guidance on working with Pipedream components and the pd dev command, you can refer to the Pipedream documentation on CLI Development Mode and deploying components: CLI Development Mode. If you continue to face issues or if the problem is different from what I’ve assumed, could you provide more details about the steps you’re taking and the exact problem you’re encountering?