Hello friend!

Currently the API only interacts with our platform, where the script executes on the server itself. This will mean that the API considers everything to be complete with the droplet moves to an active state. You’re right to note that this doesn’t help you to know when everything you’ve queued up is actually complete, as the cloud-config script runs on the droplet after the droplet is in an active state.

What I propose is that you have the cloud-config script make an external call as a last step to signal it’s completion. As it goes in a top down order, the last action completing should signal that the previous actions were completed (not necessarily successfully or in the intended way, but completed regardless).

I can give an example of something I might do. Let’s say the purpose of my droplet is a web server. I might have it write a file in /var/www/html as the last action, and have my script check for that file every X seconds, declaring the function to be complete after finding that file (maybe adding in a timeout in case of failure).

Kind Regards,
Jarland