Roman Dodin
Roman Dodin
Hi all, Can we have another review round on this? We've been using this extension privately and it is super useful, I promise :D
bumping for it to not get autoclosed
@dplore are you referring to a behavior when a set request leads to saving dynamic configuration to a persistent storage -- e.g. making current running config saved to a file...
There are applications that might require quite some number of consecutive sets (e.g. atomic-based configuration management systems that manage "small" configuration regions and thus responsible for sending changes to these...
@robshakir you mentioned > we have expected Set to persist configuration before Since this was not expressed in the spec I fear it might not be the case with implementations...
without logs it is impossible to tell you can use prototext or protojson output format to see the raw values sent to the target
please format the code snippet with triple backticks ```` ``` your output goes here ``` ```` And I believe you're not providing the expected inline value, your path `/interfaces/interface[name=et-0/0/4]/subinterfaces/subinterface[index=0]/ipv4/addresses/address[ip=11.11.11.1]` points...
you often can, but you will have to provide the json string inline, and escape all the characters that would otherwise mean an element delimiter, for instance. inline values are...
Could it be that your ingress terminates tls and sends http towards the server that expects tls? Or vice versa
this is likely a gh rate limiting in action you can invoke curl separately and see the contents of the downloaded file