Alex Lo

Looking into this more, there's two options: A. Hack solution: convert strings to numbers in [getRange()](https://github.com/cloudspannerecosystem/autoscaler/blob/79a5da7b2c4599e56c17b1d8ae2678009000c386/src/scaler/scaler-core/scaling-methods/base.js#L84) B. Better solution: parse/validate [on JSON load](https://github.com/cloudspannerecosystem/autoscaler/blob/79a5da7b2c4599e56c17b1d8ae2678009000c386/src/scaler/scaler-core/index.js#L461) A is terrible but B is bigger...

I have tested unreleased V3 and this solves the problem. Thanks @nielm

I will amend to note that storage can be zero. The CPU metrics still cannot be from what I can tell.

Xargs PR split off: https://github.com/cloudspannerecosystem/autoscaler/pull/392 Re project_id as variable vs project_id as implicit input from Google Provider. Right now the modules I am updating are split brain on the project_id...

I may be overstating the direction at the Google Provider level, at the Module level I think it should have one way in. If you think it should be consolidated...

Also I am realizing this may be a breaking change if these modules are used with a provider set to projectA and an project input of projectB (which I think...

I think blocked by https://github.com/cloudspannerecosystem/autoscaler/pull/390