Helm is converting my git tag to exponential form

[owenmorgan]

Using the git hash in my charts, and passing it as a cli argument, its messing up my tag in the rendered template.

Helm v2.3.0

Deployment.yml

..
containers:
        - name: "{{.Values.image.name}}"
          image: "{{.Values.image.registry}}/{{.Values.image.name}}:{{.Values.image.tag}}"

CLI
helm upgrade --dry-run --debug --install --wait test --values values-UAT.yaml --set image.tag=9765483 .

USER-SUPPLIED VALUES:

image:
     tag: 9765483

COMPUTED VALUES:

image:
  tag: 9.765483e+06

[yuvipanda]

When I ran into this (I was specifying values inside a yaml file), putting quotes around them solved it for me.

[owenmorgan]

thanks. tried quotes in the command line and still see the issue.

helm upgrade --dry-run --debug --install --wait test --values values-UAT.yaml --set image.tag="9765483" .

COMPUTED VALUES:
   tag: 9.765483e+06

[databus23]

Duplicate of #1707

[michelleN]

yeah that's strange. we'll need to look into this.

[wieslaw-gat]

Also experiencing this & no workaround from the related issues seems to work.

[owenmorgan]

hello, any update on this?

[bacongobbler]

Can you try --set image.tag=\"9765483\"? The --set parser takes quoted values as the value, so you might need to escape it in order to quote them on the command line.

Seems to work for me:

><> helm template chart/draftd/ --set image.tag=\"8675309\" | grep 675
        image: "microsoft/draft:"8675309""
><> helm template chart/draftd/ --set image.tag="8675309" | grep 675
        image: "microsoft/draft:8.675309e+06"

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[bacongobbler]

closing as a duplicate of #1707 as previously pointed out.