Revision not matching tag problem

Solve this by leveraging Argocd built env vars. Both of the env vars in this example will match the revision they belong too. The values are resolved against the provided revision, so if its a branch name it will stay in sync with the branch name.

helm:
  parameters:
    - name: image.tag
      value: $ARGOCD_APP_REVISION

helm:
  parameters:
    - name: image.tag
      value: $ARGOCD_APP_REVISION_SHORT_8