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

Estimate impacts of an existing inventory #352

Closed
demeringo opened this issue Oct 9, 2023 · 1 comment · Fixed by #505
Closed

Estimate impacts of an existing inventory #352

demeringo opened this issue Oct 9, 2023 · 1 comment · Fixed by #505
Assignees
Labels
documentation Improvements or additions to documentation draft feature draft feature enhancement New feature or request help wanted Extra attention is needed

Comments

@demeringo
Copy link
Collaborator

demeringo commented Oct 9, 2023

Problem

We can not get impact estimations of an arbitrary (simulation) or previously created (from-the-past) inventory. Cloud scanner only allows to request impacts of current inventory (live inventory).

Solution

Cloud scanner provides a json inventory format (output) that allow to export an inventory state.

  1. Using the ìnventory` command we could export an inventory (as json) at date-1.
  2. Add a new CLI option like estimate-from-json that could load the saved inventory, and launch it at date-2 (later).

This would allow to assess historical inventory (as it was on date-1) with the data of Boavizta API or other (as it is on date-2).

In the end, it allows easier comparison of results

  • in time (if Boavizta figures / calculation method) evolve
  • with different referentials

It would also allow a different use case: simulate the impacts of different variants of inventory / architectures

Alternatives

We could store historical data in cloud scanner, but we prefer not to do it, to keep cloud-scanner as stateless and light as possible.

We consider that the storage / versioning of historical data is not a cloud-scanner concern and should be handled by a specific tool.

Additional context or elements

We should also consider if the inventory capabilities of cloud-scanner should be maintained in a separate module.

@demeringo demeringo added documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed draft feature draft feature labels Oct 9, 2023
@demeringo
Copy link
Collaborator Author

Consider also using a CSV or XLS to import inventory, could be easier for end user to estimate impacts.

@demeringo demeringo changed the title Get impact assesment of a previously saved inventory Estimate impacts of an existing inventory May 13, 2024
@demeringo demeringo self-assigned this May 13, 2024
@demeringo demeringo linked a pull request May 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation draft feature draft feature enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant