To satisfy specific ordering requirements around IP assignment (before VM existence) and Security Group assignment (after VM existence but before use), the administrator usesPre-createandPost-createtasks.
Pre-Create Task (IP Address):This task executesbeforethe VM provisioning call is made to the provider. The developer uses this phase (e.g., an HTTP task or Script) to request a specific IP from an external IPAM solution. The IP is stored in a variable and passed to the VM configuration.
VM Provisioning:The VM is created (using the IP from step 1) but is configured in the blueprint to stay in aPowered Offstate initially.
Post-Create Task (Security Group):This task executesimmediately afterthe VM resource is created (so the VM UUID/NIC exists) but before the application logic starts. The developer uses this phase to make an API call (e.g., to Flow or NSX) to place the VM into the required Security Group.
Power On:A subsequent task (or manual action) powers on the VM, ensuring it boots up with the correct IP and within the correct security boundary.
Option C is the only combination that covers both the "Before Creation" and "After Creation" phases required.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit