This topic was automatically generated from Slack. You can find the original thread here.
Hi Rhys, the key doesn’t necessarily need to match the file name.
But I believe the issue is that you’re trying to use the update CLI command which is only intended for deployed source updates.
Could you try pd publish instead? That is intended for publishing actions and updates
Its already deployed
still no luck
That error means that the workspace ID flag is missing. Components are deployed to specific workspaces
can you show me how to find my workspace ID and how to pass it as an argument to the pd publish CLI command?
To find your workspace ID, follow these steps: 1. Visit your Pipedream dashboard at https://pipedream.com/workspaces. 2. Click on the workspace you want to find the ID for. 3. In the workspace settings, you’ll find the workspace ID. Once you have your workspace ID, you can create a profile in your Pipedream config file with the following information: [profile_name] api_key = <API Key from workspace settings> org_id = <Workspace ID from workspace settings> Replace <API Key from workspace settings> with your API key and <Workspace ID from workspace settings> with the workspace ID you found. Now, when using the pd publish CLI command, pass the --profile <profile_name> flag. For example, if you named your profile my_workspace, you’d run this command to publish a component: ```
bash pd publish file.js --profile my_workspace
When was this changed? I never needed to specify a workspace
it seems like the workspace doesnt exist but it clearly does going from the UI and the fact that i cant create a new workspace with the same name
pd login proves that im logged in
where do i find the pipedream config file to set my workspace id
To find the Pipedream config file, follow these steps: 1. Open your terminal or command prompt. 2. Run the following command to find the location of your Pipedream config file: bash pd config path This command will return the path to your Pipedream config file. Once you have the path, open the config file in your preferred text editor. To create a new profile with your workspace ID, add the following information: [profile_name] api_key = <API Key from workspace settings> org_id = <Workspace ID from workspace settings> Replace <API Key from workspace settings> with your API key and <Workspace ID from workspace settings> with the workspace ID you found. Save the changes to the config file. Now, when using the pd publish CLI command, pass the --profile <profile_name> flag. For example, if you named your profile my_workspace, you’d run this command to publish a component: ```
bash pd publish file.js --profile my_workspace
how do i update the cli
To update the Pipedream CLI, you’ll need to download the latest version for your operating system and architecture from the CLI Builds table found at Installing the CLI. Here are the download links for each OS and architecture: - Linux (amd64): https://cli.pipedream.com/linux/amd64/latest/pd.zip - Linux (386): https://cli.pipedream.com/linux/386/latest/pd.zip - Linux (arm): https://cli.pipedream.com/linux/arm/latest/pd.zip - Linux (arm64): https://cli.pipedream.com/linux/arm64/latest/pd.zip - macOS (amd64): https://cli.pipedream.com/darwin/amd64/latest/pd.zip - Windows (amd64): https://cli.pipedream.com/windows/amd64/latest/pd.zip Download the appropriate build for your system, unzip the archive, and replace the existing pd binary with the new one. Make sure the updated pd binary is placed somewhere in your PATH. After updating the CLI, you can run pd to see a list of all commands, or pd help <command> to display help docs for a specific command.