Automation

As you've correctly clocked, service provisioning with Apstra is composed of many layers, with each layer depending on the ones before it. A typical dependency graph might look like: template -> blueprint -> routing zone -> virtual network -> connectivity ...

You are correct that the Terraform provider is the right approach for provisioning automation. It does support making incremental changes to existing blueprints. Take a look at this example for adding a virtual network. https://registry.terraform.io/providers/Juniper/apstra/latest/docs/resources/datacenter_virtual_network ...

Hi! Could you try to do the same in the CLI Shell of this device (commit check)? It will be clear which lines the checker doesn't like. ------------------------------ Yevgeniy Voloshin ------------------------------

Additional question, should the Terraform implementation work with OpenTofu? ------------------------------ CIRO IRIARTE ------------------------------

I'm about to give up trying to use Apstra CLI, documentation is scarce and seems to be meant to platform maintenance and not service provisioning. I've seen there's a Terraform provider but it's not clear to me: Can it handle partial configuration ...

Hi Can anyone help me with this error, I am using the CLI editor. ------------------------------ HADRIAN MULHERN ------------------------------

Hi, As i remember, Paragon active assurance can do multivendor. U just need to spin up the vm as end device and that end device must register in the Paragon Cloud. U can try as Juniper SE in in your country. Thanks