As currently written, the last thing we do in linode_create.yml must be to force users to change their password, because once we do that, we can't do anything else! (Until we change our password, of course.)
Since handlers run in the order they are defined, not the order listed in the notify statement, our current implementation relies on our handlers being written down in the correct order, which seems fragile.
We should find some more reliable way to do this, perhaps calling the second handler from the first handler. We also should check whether this issue exists elsewhere in our repository, and fix any other occurrences in a similar fashion.
As currently written, the last thing we do in linode_create.yml must be to force users to change their password, because once we do that, we can't do anything else! (Until we change our password, of course.)
Since handlers run in the order they are defined, not the order listed in the notify statement, our current implementation relies on our handlers being written down in the correct order, which seems fragile.
We should find some more reliable way to do this, perhaps calling the second handler from the first handler. We also should check whether this issue exists elsewhere in our repository, and fix any other occurrences in a similar fashion.