sf/sfdx command to retrieve all package names #2338
jxbambrick
started this conversation in
Ideas
Replies: 3 comments
-
This issue has been linked to a new work item: W-13644957 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'd also like this feature; we do something similar on several of my projects. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
As part of a deployment pipeline, I use sf to download one or more change sets (up to 100 change sets at a time). The sf command will error when a change set doesn't exist, or the name is not passed correctly (due to special characters or spaces). The only way to confirm that a change set exists is to run the command "sf project retrieve start --package-name placeholder --json" and check the status code returned. This can take several minutes to run, depending on the size of a single change set. Downloading multiple large change sets (50 or more) can take up to an hour.
There also isn't an option to retrieve a list of all the change sets in an environment.
What are you trying to do
As part of a deployment pipeline the command "sf project retrieve start --package-name placeholder1 --package-name placeholder2 --package-name placeholder3...--package-name placeholder100 --json" will fail but only show the error for the first missing or misspelled change set breaking the pipeline and taking time to manually resolve. The only way to confirm all the change sets is to run the command independently for each change set, confirm that status, and add the failed change set to a list.
Describe the solution you'd like
I would like two commands:
Describe alternatives you've considered
The only way to confirm all the change sets exist is to run the command independently for each change set, confirm that status, and add the failed change set to a list.
Additional context
Beta Was this translation helpful? Give feedback.
All reactions