dashboard/billing/migrations
Aravinth Manivannan b12cc044da
ci/woodpecker/push/woodpecker Pipeline was successful Details
fix: Invoice generation must not consider deleted VMs' names for
checking if payment is already fulfilled

DESCRIPTION
    Invoice generation is dependent on instance_name. Deleting a VM
    doesn't delete the corresponding payments record since payment
    receipts should be preserved for accounting purposes.

    But being heavily dependent on instance_name, without taking deleted
    VMs into account produces incorrect behavior under certain
    circumstances: if a VM named 'foo' is paid for and is deleted before
    its billing cycle is competed and a new VM is created with the same
    name, either by the same user or a different user, invoice won't be
    generated for the new VM since a payment record already exists for
    that billing cycle for the VM named 'foo'.

    Marking deleted VMs' payment records unsuitable for checking if a VM
    is already paid for will result in correct behavior.

fixes: https://gitea.hostea.org/Hostea/dashboard/issues/38
2022-07-08 22:28:39 +05:30
..
0001_initial.py feat: implement billing with stripe 2022-06-22 00:37:03 +05:30
0002_alter_payment_billing_address_1_and_more.py feat: implement billing with stripe 2022-06-22 00:37:03 +05:30
0003_delete_paymentdetail.py feat: implement billing with stripe 2022-06-22 00:37:03 +05:30
0004_payment_billing_pay_paid_by_77f57c_idx.py feat: implement billing with stripe 2022-06-22 00:37:03 +05:30
0005_payment_vm_deleted.py fix: Invoice generation must not consider deleted VMs' names for 2022-07-08 22:28:39 +05:30
__init__.py feat: implement billing with stripe 2022-06-22 00:37:03 +05:30