Fix: vm_cost_views missing join with status #684
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Vm_cost_view needed a join with message_status to avoid having a forgotten vms taking into account on
locked_ammount
Related Clickup or Jira tickets : ALEPH-None
Self proofreading checklist
Changes
This pull request includes a significant update to the
vm_costs_view
in the database schema to include themessage_status
field. This change ensures that only VMs with a processed status are considered in the view.Database Schema Update:
deployment/migrations/versions/0030_d8e9852e5775_fix_compute_message_status_on_vm_cost_.py
: Added a new migration script to update thevm_costs_view
to include themessage_status
field and filter VMs based on the status 'processed'. This ensures that only processed VMs are included in the view.