-
Notifications
You must be signed in to change notification settings - Fork 82
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update the .zap file when Studio project updates to a new GSDK (#1431)
- Update the uc_upgrade target for apack.json - Add the upgrade zap file function which updates the top level json packages for the .zap file based on the gsdk being used for the project. - The code goes through a temporary directory where .zap files are stored for Studio and updates all the .zap files in that directory - The top level upgrade packages are matched based on type and category - Other minor cleanup - Cleaning up the directory flag to -d and adding the no load failure flag when packages are not present - Adding unit tests for the upgrade process - JIRA: ZAPP-1362
- Loading branch information
Showing
12 changed files
with
6,212 additions
and
33 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.