var to ref git sha1 or version info in becep

[tg123]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

var ver = deployment().properties.cvsver

resource xxx xxx = {
 name: '{xxx$ver}
}

Describe the solution you'd like
A clear and concise description of what you want to happen.

add version info into deployment() or some other build time/runtime obj

[stephaniezyen]

Can you please give more information on what you are looking for and what issue you are having?

[tg123]

bicep build put some meta info into output.json

for exmaple

  "metadata": {
    "_generator": {
      "name": "bicep",
      "version": "0.24.24.22086",
      "templateHash": "2004619805940471825"
    }
  },

could bicep add git sha1 or some version info, so it is easier to track version deployed

[jeskew]

The git sha is probably a little too specific to a particular project structure to be implemented within Bicep core. @tg123 would your needs be covered by something like #7259?

[tg123]

go support build vcs info to final binary
https://portal.microsofticm.com/imp/v3/incidents/details/459821378/home

i think bicep can do the same

[jeskew]

Make sense! Triaging as a standalone feature request.

If we do ship #7259 before anyone works on this (and since this task has no milestone, there is no guarantee that anyone will ever pick this up), there will be a viable way to do this without explicit support in the Bicep compiler.