Many NS/VNF projects are under git version control. It is helpful for CI pipelines to continuously track versions among the generated artifacts. So it seems a nice feature to let the packager automatically set the version field to the commit hash of the project used to generate the package.
Feature is optional and needs an activation flag: --use-commit-versions or so.
tng-pkg needs to auto-sense if the used project is in a git repo or not. If not, the manually entered version of the commit message would be used.
Many NS/VNF projects are under git version control. It is helpful for CI pipelines to continuously track versions among the generated artifacts. So it seems a nice feature to let the packager automatically set the version field to the commit hash of the project used to generate the package.
Feature is optional and needs an activation flag:
--use-commit-versionsor so.tng-pkg needs to auto-sense if the used project is in a git repo or not. If not, the manually entered version of the commit message would be used.
Priority: Nice to have, but not important.