You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloud scanner does not return details about the components that leads to a result.
Which prevent us to understand the impact of RAM vs CPU for example.
Solution
Have an optional flag or parameter that add verbosity to the json output.
It should return the equivalent content (list of components and impacts) that are returne by the Boavizta API when used in verbose mode.
⚠ WARNING: It seems that in Boavizta API, The results of Verbose mode do not correspond to the instance, but to the entire server that host an instance. In verbose mode, no ratio is applied to the impacts of components (contrary to non-verbose API output where a ration corresponding to the number of instances per servers is applied before returning results).
add a raw_data key to the cloud-scanner json output: It will always contain the raw_output of Boavizta API. The rationale is that if API evolves, we benefit from or can parse an additional field that is not managed by cloud-scanner.
Add a verbose flag or parameter (default to false) to the cloud-scannner commands or routes. If active, it will trigger the verbose output of the Boavizta API (which we will retrieve in the new raw_data field.
Problem
Cloud scanner does not return details about the components that leads to a result.
Which prevent us to understand the impact of RAM vs CPU for example.
Solution
Have an optional flag or parameter that add verbosity to the json output.
It should return the equivalent content (list of components and impacts) that are returne by the Boavizta API when used in verbose mode.
⚠ WARNING: It seems that in Boavizta API, The results of Verbose mode do not correspond to the instance, but to the entire server that host an instance. In verbose mode, no ratio is applied to the impacts of components (contrary to non-verbose API output where a ration corresponding to the number of instances per servers is applied before returning results).
See discussion in Boavizta API Q/A: Boavizta/boaviztapi#221
Alternatives
Additional context or elements
The text was updated successfully, but these errors were encountered: