Is there an equivalent of cloud-init status --wait?

Is there an equivalent of cloud-init status --wait of cloud-init in cloudbase-init?

[rgl]

My example VM ended-up with these registry keys/values:

The registry key b3d1dc735800195b8f62 seems to be the value of instance-id property that is inside the cidata meta-data json file, is that correct?

From an external viewpoint, how do we known how many plugins exist?

How do we known when all the plugins are “done” (it seems that not all plugins end-up with the same value)?

And how we do this in a way that is not tied with a specific cloud or plugin?

I think we should have a command available in the cloudbase-init package that deals with all this; I can propose one when the questions above are cleared up 😃

For reference, this is what cloud-init returns:

vagrant@example:~$ cloud-init status
status: done
vagrant@example:~$ cloud-init status --wait

status: done
vagrant@example:~$ cloud-init status --wait --long

status: done
time: Mon, 12 Oct 2020 18:05:43 +0000
detail:
DataSourceNoCloud [seed=/dev/sr0][dsmode=net]

This is also described at https://cloudinit.readthedocs.io/en/latest/topics/cli.html#cli-status.

[WeetA34]

as a workaround, we’re using the following powershell:

while ((Select-String -Path 'C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log\cloudbase-init.log' -Pattern '^.+Plugins execution done$') -eq $null) { Write-Host -NoNewLine '.'; Start-Sleep -Seconds 5 }