Automation

Yes, I understand. However, using "plain-text-password-value" still gives the same error message: "minimum-character-changes configured, use plain-text-password in cli to configure password". I'm using Ansible 11.3.0, and Ansible-core 2.18.3. This problem ...

Which version of Ansible are you using? Thanks.

That is why I suggest to use plain-text-password-value and not plain-text-password Regards,

Hi, thank you for the response. I've tried this approach already, along with just using "plain-text-password". The former produces the same error message as the encrypted-password method, and "plain-text-password" is only meant for CLI changes. ------------------------------ ...

Probably it is complaining about encrypted_password ? Perhaps try this approach instead. --- # Playbook to change the password on Juniper Switches - name: Change password on Juniper Switch hosts: Juniper_ex4300 # Switch group from inventory ...

So, with a "commit script", the scenario is that the script is going to process whatever the user is attempting to commit. Either to issue a warning, block the commit, or make some additional adjustments to the commit that has triggered the commit script. ...

Sorry, I was wrong. Please ignore my previous post. I have only ever used jsc.emit_change(content,'change',format) in commit script. "format" is only support XML. I don't know of any cases where functions other than jsc.XXX() have been used in a commit ...