server: return next_actions
data on create
#72
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a server is created, it can return a field
next_actions
containing actions that will be executed after the server was created. Most commonly, this containsstart_server
. But for example if we directly pass networks or firewalls, it also contains the actions for adding the server to the network or applying the firewall to the server.To cleanly start a server and wait for all actions to complete, we need to know these
next_actions
.Example from a test run: