You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Currently there is already the -p flag that lets you select specific packages in a bundle to deploy. This is great when you want to test deploying a specific package or a few packages from the bundle. However there is currently no flag to do the inverse of that. During development there are times when I want to deploy a whole bundle except for 1 or 2 packages. Currently this requires using the -p flag and listing every other package in the bundle I don't want to exclude.
Describe the solution you'd like
Given a bundle that contains a set of packages
When I run a dev deploy with the --placeholder flag and a list of packages
Then the bundle deploys but skips the packages listed for the new flag
Additional context
This is primarily an improvement for bundle developer experience so I am fine with this new option only being added to the dev deploy command instead of the regular deploy command to keep things simple for end users consuming bundle artifacts.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
Currently there is already the -p flag that lets you select specific packages in a bundle to deploy. This is great when you want to test deploying a specific package or a few packages from the bundle. However there is currently no flag to do the inverse of that. During development there are times when I want to deploy a whole bundle except for 1 or 2 packages. Currently this requires using the -p flag and listing every other package in the bundle I don't want to exclude.
Describe the solution you'd like
Additional context
This is primarily an improvement for bundle developer experience so I am fine with this new option only being added to the dev deploy command instead of the regular deploy command to keep things simple for end users consuming bundle artifacts.
The text was updated successfully, but these errors were encountered: