Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow wildcards in force:source:retrieve/deploy #2386

Closed
WillieRuemmele opened this issue Aug 1, 2023 Discussed in #2363 · 1 comment
Closed

Allow wildcards in force:source:retrieve/deploy #2386

WillieRuemmele opened this issue Aug 1, 2023 Discussed in #2363 · 1 comment
Labels
bug Issue or pull request that identifies or fixes a bug validated Version information for this issue has been validated

Comments

@WillieRuemmele
Copy link
Member

Discussed in #2363

Originally posted by catalandres September 22, 2019
Is your feature request related to a problem? Please describe.
I am trying to download only the classes related to a project in an org. We have named them consistently with a prefix and we would like to be able to retrieve and deploy only a subset of them. That way we will not risk overwriting another team's progress by deploying a past version of a file unrelated to our project.

What are you trying to do
See above.

Describe the solution you'd like
sfdx force:source:retrieve -m 'ApexClass:SomePrefix_*' should put in the classes folder only the classes that begin with SomePrefix_.

Describe alternatives you've considered
The one alternative that I can think for a wildcard retrieval would be to manually delete any files that are not in scope after the retrieval.
The alternative to a deployment with a wildcard (if it is not viable to delete files upon retrieval) is to list all the necessary classes one by one.

Additional context
Not applicable.

@WillieRuemmele WillieRuemmele added bug Issue or pull request that identifies or fixes a bug validated Version information for this issue has been validated labels Aug 1, 2023
@git2gus
Copy link

git2gus bot commented Aug 1, 2023

This issue has been linked to a new work item: W-13867893

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

2 participants