YAML tries to interpret things that aren't in quotes as numbers and then
falls back to strings. Also, your shell would be trying to interpret "" on
the command-line. I think the syntax would be
> It appears "number" is the proper type for a floating point value. My
> use of type: float in config.yaml worked in juju 1.25.6. Perhaps the
> types changed between versions. Will use "number" for this solution,
> but more useful expounding upon available types in the upgrade-charm
> check would be helpful.
>
> Lastly, a number should be acceptable as a string, though I know it's
> not a strong type-cast, string should be allowed by juju run-action
> var=<number>.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1714405
>
> Title:
> actions.yaml schema does not support "float"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1714405/+subscriptions
>
YAML tries to interpret things that aren't in quotes as numbers and then
falls back to strings. Also, your shell would be trying to interpret "" on
the command-line. I think the syntax would be
juju run-action ... --value="'2.9'"
John
=:->
On Sep 1, 2017 07:50, "Drew Freiberger" <email address hidden> wrote:
> It appears "number" is the proper type for a floating point value. My /bugs.launchpad .net/bugs/ 1714405 /bugs.launchpad .net/juju/ +bug/1714405/ +subscriptions
> use of type: float in config.yaml worked in juju 1.25.6. Perhaps the
> types changed between versions. Will use "number" for this solution,
> but more useful expounding upon available types in the upgrade-charm
> check would be helpful.
>
> Lastly, a number should be acceptable as a string, though I know it's
> not a strong type-cast, string should be allowed by juju run-action
> var=<number>.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> actions.yaml schema does not support "float"
>
> To manage notifications about this bug go to:
> https:/
>