cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
375
Views
0
Helpful
0
Replies

validate_no_change_after_system_deploy allows to delete the node

presunda
Cisco Employee
Cisco Employee

Hello, 

I had a scenario where I had to restrict configuration change for leaf nodes when the system is running.

 

container topcontainer {
        tailf:info "TLS keystore configuration for Interfaces";
        tailf:validate validate_no_change_after_system_deploy {
           tailf:dependency ".";
           tailf:opaque "no-new-instance";
        }
 
    list list1{
            tailf:validate validate_no_change_after_system_deploy {
               tailf:dependency ".";
               tailf:opaque "no-new-instance";
            }
            tailf:info "list1";
            key "name";
            leaf name {
            tailf:validate validate_no_change_after_system_deploy {
               tailf:dependency ".";
               tailf:opaque "no-new-instance";
            }
        }
    }
}
 

Am not able to create new topcontainer/list1 when the system is running – which is expected.

However, I am able to delete topcontainer/list1 – which is unexpected. I would not want to delete them when system is running.

Am I missing something ? Or any other annotation that I need to include to restrict the delete operation when system is in running mode.

 

Thanks,

Prem

 

0 Replies 0