Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cf env *appname* shows number in scientific format #961

Closed
vmovva opened this issue Sep 15, 2016 · 2 comments
Closed

cf env *appname* shows number in scientific format #961

vmovva opened this issue Sep 15, 2016 · 2 comments

Comments

@vmovva
Copy link

vmovva commented Sep 15, 2016

User provided service with number longer than 10 digits as value gets converted into scientific format when cf env *appname* is issued.

  • Reproduction steps :
  1. Create a CUPS : cf cups longnumbertest -p '{"longNumber":1234567890}'
  2. Bind it to an application
  3. Perform cf env appname
  4. Notice that output shows something similar to :

"user-provided": [
{
"credentials": {
"longNumber": 1.23456789e+09
},
"label": "user-provided",
"name": "longnumbertest",
"syslog_drain_url": "",
"tags": []
}
]

Expectation is that cf env would show number in human readable format , 1234567890
Note: cf curl /v2/apps/appGUID/env shows human readable number format.

  • CLI Version
    cf version 6.21.1+cd086c8-2016-08-18
  • CC API Endpoint Version
    235
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/130489629

The labels on this github issue will be updated when the story is started.

@vmovva vmovva changed the title cf env *appname* cf env *appname* shows number in scientific format Sep 15, 2016
@dkoper dkoper added the wontfix label Sep 29, 2016
@dkoper
Copy link

dkoper commented Sep 29, 2016

There seems to be a related limitation in Golang.

My team tried fixing it but it required changes in code that is used by a lot of commands, and tests started failing after the change.
If it were a simple fix, we'd do it, but as it seems complicated with high risk of introducing regressions, we won't fix it at this time.
We may revisit this at a major version upgrade when the functionality of related commands can be changed.

Cheers,
Dies Koper
CF CLI PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants