Why do you need to change the IP address of a Droplet so often?

@spenglert

Using a while loop to check the status is most likely going to be the best route, though each action does provide started_at and completed_at times, which could be used to verify when an action is started and when it completes.

You could use date/time comparison to verify completion, though you’d still be using a while loop as means to continue to check.

The only issue to consider here is that if the continuous IP swapping as a result of scraping ends up resulting in numerous IP’s being blocked and sent to blacklists, you may potentially risk your account being suspended. This doesn’t mean you will be, though it is something I would be cautious of. Since the IP’s your flushing in and out are reassigned to other users, if they are blocked, either the next user or DigitalOcean has to spend time (and potentially money) to get those IP’s cleaned up.

Hey @spenglert,

I had to do something like this for SnapShooter.io

The solution we went for was giving the snapshot a unique name. We start the snapshot and store the action id. We then keep pooling the action via its ID to see if its status changes to completed.

Once we have a completed status we then look through all of the accounts snapshots and match up the unique name we gave it. We then know the snapshots Id for later use.