At the moment CSM does not support the possibility of using git tags to assign commit ids to CFS configuration layers, this is an issue because it forces users to use commits if they want to have inmutable CFS configuration layers or mutable by using the most recent commit if CFS configuration is updated.
A proposal is to add a new git tag support for CFS configuration layers.
Upon CFS configuration creation, if tag is defined for a CFS configuration layer, then, manta/mesa will check if that layer exists in gitea, fetch its commit id and assign it to the CFS configuration layer.
If both branch and tag are defined, then, the application should crash.
Tasks:
Add tag to CFS configuration layer to mesa struct
get gitea commit id related to git tag and assign commit i to cfs configuraion layer.
repeat previous step for all CFS configuration layers
If any layer fails, then, cancel transaction, otherwise create CFs configuration
At the moment CSM does not support the possibility of using git tags to assign commit ids to CFS configuration layers, this is an issue because it forces users to use commits if they want to have inmutable CFS configuration layers or mutable by using the most recent commit if CFS configuration is updated. A proposal is to add a new git tag support for CFS configuration layers. Upon CFS configuration creation, if tag is defined for a CFS configuration layer, then, manta/mesa will check if that layer exists in gitea, fetch its commit id and assign it to the CFS configuration layer. If both branch and tag are defined, then, the application should crash.
Tasks: Add tag to CFS configuration layer to mesa struct get gitea commit id related to git tag and assign commit i to cfs configuraion layer. repeat previous step for all CFS configuration layers If any layer fails, then, cancel transaction, otherwise create CFs configuration