This commit does not change any of the existing functionality.
Both commands for publishing and pulling bundles now has an extra flag --use-commit:
If the flag is passed, the command will attempt to retrieve the commit hash from the git branch and use that as the bundle ID. When pulling with the flag, the bundle ID from the lasso-bundle.json file will be ignored, and the git commit will be used for the zip file name.
This is useful in the scenario where the user wants the bundles to coincide with the git hashes, adding the following 2 advantages:
1) The bundles can be generated during the CI pipeline, without having commit or upload the bundle file to the filesystem.
2) Rolling back to previous commits ensures that the corresponding bundle is available and easily identifiable.
This commit does not change any of the existing functionality.
Both commands for publishing and pulling bundles now has an extra flag
--use-commit
:If the flag is passed, the command will attempt to retrieve the commit hash from the git branch and use that as the bundle ID. When pulling with the flag, the bundle ID from the
lasso-bundle.json
file will be ignored, and the git commit will be used for the zip file name.This is useful in the scenario where the user wants the bundles to coincide with the git hashes, adding the following 2 advantages: 1) The bundles can be generated during the CI pipeline, without having commit or upload the bundle file to the filesystem. 2) Rolling back to previous commits ensures that the corresponding bundle is available and easily identifiable.