It is currently possible for requests to be carried out on the same instance in quick succession, e.g. turning it on one minute and turning off the next. In the original visualiser application this was not possible - we should validate that this definitely works as intended, both from the AWS/Azure side, and within control.
In particular we should investigate that check_and_update_status in ActionLog works correctly here, as there is perhaps a chance that if an instance has two status changes in the time between instance logs are recorded, a change could be missed and a log stuck in 'pending'.
It is currently possible for requests to be carried out on the same instance in quick succession, e.g. turning it on one minute and turning off the next. In the original visualiser application this was not possible - we should validate that this definitely works as intended, both from the AWS/Azure side, and within control.
In particular we should investigate that
check_and_update_statusinActionLogworks correctly here, as there is perhaps a chance that if an instance has two status changes in the time between instance logs are recorded, a change could be missed and a log stuck in 'pending'.