Allow for Object Deployments without subcomponents to git
When deploying an object to git currently there is no support to ONLY deploy the object metadata.
We have a large managed package that your code requires the .object file for an object in that managed package to exist for me to deploy fields or other customizations for said object git -> org. When I deploy org -> git to get the .object file into my repo it also grabs all the fields on the managed package object which I don't want/need.
I don't want the fields and I need to specifically get it from the target org because if anything is different failures occur due to gearset trying to deploy a managed package
So I would like to have a way to either NOT require the .object record to select custom fields in a compare OR be able to fetch the .object field by itself from an org when deploying to git.
Chris Tufts
shared this idea
-
Sunny Matharu commented
this is hugely important for us and impacts our ability to use gearset in all cases.
it makes no sense for Agile development teams where there will be a mixture of object metadata in an org that is either ready, or in progress, where we only want to commit the "ready" sub-components.
it also makes it practically impossible, without VSCode or direct repo mgmt to migrate a subset of object data from one company's org to another company's org (e.g. for mergers, subsisdiary companies etc)
this is not a limitation of competing devops tools, and for all of Gearset's differentiating features, this is a huge blocker to adoption/transition.