Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Dependency Check before deploying unlocked packages #57

Closed
azlam-abdulsalam opened this issue Jun 22, 2020 · 2 comments · Fixed by #98
Closed

Dependency Check before deploying unlocked packages #57

azlam-abdulsalam opened this issue Jun 22, 2020 · 2 comments · Fixed by #98
Assignees
@aly76
Labels
new feature new feature wontfix This will not be worked on
Projects
sfpowerscripts-release
Milestone
Milestone 18

Comments

@azlam-abdulsalam
Copy link
Contributor

If an unlocked package is deployed to an org, and the dependencies are not met, the error is thrown by the platform during the course of installation. This sometime takes considerable time to surface.

We could surface this quite early, by having dependencies that was used to build this unlocked package added in the artifact metadata and have a check to see whether its already installed in the org before continuing to actual deployment
@azlam-abdulsalam azlam-abdulsalam added the new feature new feature label Jun 25, 2020
@azlam-abdulsalam azlam-abdulsalam added this to To do in sfpowerscripts-release via automation Jun 25, 2020
@azlam-abdulsalam azlam-abdulsalam added this to the Milestone 16 milestone Jun 25, 2020
@azlam-abdulsalam
Copy link
Contributor Author

@manisfdcsfdx Whats the best command in sfpowerkit to achieve this?

azlam-abdulsalam pushed a commit that referenced this issue Jul 15, 2020
#57 Skip package installation if alreay installed
a92c009
@azlam-abdulsalam azlam-abdulsalam mentioned this issue Jul 15, 2020
Closed
azlam-abdulsalam pushed a commit that referenced this issue Jul 15, 2020
Fixes #57 Add Check to determine whether a package has to be Installed
7c5938d 
This also introduces couple of things

- Introduce sfdx-node for wrapping around sfdx and sfpowerkit easily
- Refactor existing pipelines to remove the decider stage
- Update dependencies
azlam-abdulsalam pushed a commit that referenced this issue Jul 18, 2020
Fix #57 Support for skipping installation if already installed
76b09e6
@azlam-abdulsalam azlam-abdulsalam mentioned this issue Jul 18, 2020
Merged
sfpowerscripts-release automation moved this from To do to Done Jul 20, 2020
azlam-abdulsalam added a commit that referenced this issue Jul 20, 2020
@azlam-abdulsalam
Feature/skip installation (#98)
1dd22a4 
* Fix #57 Support for skipping installation if already installed

* Fix #94 Artifact is not a mandatory requirement for installation
sfpowerscripts-release automation moved this from Done to In progress Jul 27, 2020
@azlam-abdulsalam azlam-abdulsalam moved this from In progress to To do in sfpowerscripts-release Jul 27, 2020
@azlam-abdulsalam azlam-abdulsalam removed this from the Milestone 16 milestone Jul 27, 2020
@stale stale bot added the wontfix This will not be worked on label Sep 10, 2020
@azlam-abdulsalam azlam-abdulsalam added this to the Milestone 18 milestone Sep 16, 2020
@stale stale bot removed the wontfix This will not be worked on label Sep 16, 2020
@dxatscale dxatscale deleted a comment from stale bot Oct 2, 2020
@stale
Copy link

stale bot commented Nov 16, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 16, 2020
@stale stale bot closed this as completed Nov 23, 2020
sfpowerscripts-release automation moved this from To do to Done Nov 23, 2020
This was referenced Mar 11, 2022
Closed
Closed
@snyk-bot snyk-bot mentioned this issue Mar 31, 2022
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@aly76 aly76

Labels
new feature new feature wontfix This will not be worked on
Projects
sfpowerscripts-release
  
Done
Milestone
Milestone 18
Development

Successfully merging a pull request may close this issue.

Feature/skip installation dxatscale/sfpowerscripts
2 participants
@aly76 @azlam-abdulsalam