Closed maciejdzikowicki closed 4 years ago
Hi @maciejdzikowicki thanks for the report! What version are you using?
I'm using 3.4.0
I am also having this issue. You can get around it by adding the tag 'GIT_TAGS' to the function manually. You lose the usefulness of the tag, but it's available as in env var. @jacob-meacham maybe add the ability to disable env vars and tags separately version all or none. Like:
exportGitVariablesToTags: false
exportGitVariablesToEnv: true
or fix the tag output to adhere to the required regex.
Thanks @maciejdzikowicki @dvictory! I just published two new releases: 3.5.0 includes the ability to specify a whitelist of variables that you'd like to set on tags/env - see the README for using it. 4.0.0 changes the tags separator from ',' to '::' which should conform to the AWS regex but is a breaking change so I wanted to rev bump.
When more then one tags points to a commit, deployment fails with following exception: