1

According to Develop Against Any Org, there's a new (at least new to me since Summer '19) option -o for the sfdx deploy command as follows:

sfdx force:source:deploy -o

Documentation says:

Regardless of whether the deployment contains errors (not recommended if deploying to a production org)

What would be a good use case for this? And would there be any good use case to ever deploy to production for this?

Improve this question

1 Answer 1

Reset to default
4

For production, it seems to only apply to deployments that do not fail because of unit tests. For example, if you deploy a bunch of fields and a page layout, and one field fails to deploy, the layout will also fail, but the remaining fields may succeed. It allows a partial update to happen. For Sandboxes, this can be very important, as it allows you to ptoentially deploy broken changes to the Sandbox so you can fix them.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .