Automation

Thank you, shortly after posting this i did try this route and it worked. I apprechiate the fast reply. I will post the playbook that i have gotten working in case anyone in the future comes across the same issue --- - name: Change Password on Junos ...

For root password changing, I use the juniper_junos_config module and update the configuration with "set system root-authentication plain-text-password-value {{ new_pw }}".

I have been reading some docs on the Junipernetworks.junos collection, here is the section for the .junos_user module https://docs.ansible.com/ansible/latest/collections/junipernetworks/junos/junos_user_module.html I have this playbook --- - ...

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 ------------------------------