Allow deployment of unlocked packages
At the moment, you can select "Installed package" as a metadata type to compare, and I think you can use this to install a package (without installation key).
However, unless I'm missing them, 2nd Generation Unlocked packages don't appear in a comparison like this.
It would be really useful to be able to deploy 2GP with Gearset because I sometimes need to make metadata changes at the same time as installing
e.g. I'm moving some old functionality into an Unlocked package and that old code has logic in the triggers. I want to be able to delete the old triggers at the same time as installing an Unlocked package that implements the logic via a trigger framework. Right now, I'm working around it by including an empty trigger with the same name in my 2GP. That wipes out the old one on the first install, then I need to do another package version to remove the empty trigger.
Aidan Harding
shared this idea
-
Jeff
commented
Without trying to solution, I could envision a way to provide GS a view into the .sfdx/someorg/sourcePathInfos.json Granted, this file isn't under source control, but could be moved to a special location so not to disrupt DX and support GS. This file contains all the file locations and may be able to help GS with a source to org deployment. The inverse, pull new org to source, may require a default drop folder and then the dev can refactor/move to preferred location.
-
[Deleted User]
commented
Ran into this with the Unofficial SF unlocked package: FlowScreenComponentsBasePack; I have to install this manually in each target org