Rare project developers

[Alexander Gall <>]

On Fri, 8 Apr 2022 10:27:46 +0200, mc36 <> said:

> hi,
> On 4/8/22 09:38, mc36 wrote:
>> 
>> i'm writing you that my idea here is a new knob: "alias exec asdf 
>> sticky-onlychanged"
>> then it'll be executed only if the parameter changed...
>> it's a redundant check because you already implemented it but imho it's 
>> the way to go....
>> and imho we'll need an other knob, "alias exec asdf sticky-onlysuccess"
>> which will remember the last choice only if the execution went well...

> with this smaller change
> https://github.com/mc36/freeRouter/commit/a3a43ef7c83b4caa267e4760ba8b17fc340220a2

So, "persistent" means that the sticky alias is not executed when
booting?  This means that I will have to bring the initial p4-profile
file back to the ONIE installer. Otherwise, the system won't come up
when it is booted the first time.

Also, something seems wrong. When I activate all of those options, I
get this after a boot:

rare#show config-differences                                                  
                                                                              
                                                                    
no alias exec tna-set-profile sticky-param PE
alias exec tna-set-profile sticky-param

> we just got a lot more parameters, imho we'll need all of these set for the 
> profile to work as intended...

Yes, lots of parameters to fix corner cases :/ Maybe we need to
redesign this?  We could add a hidden parameter to a sticky command
that would indicate the context in which it is executed, e.g. from CLI
or not, during the boot process or something like that. We'd have to
pick something that could cover all the cases we've seen so far.

With that, we could avoid the "persistent" option, but if we insist
that the command returns success (so it doesn't show up as an apparent
problem in the log during boot), we would still perform an unnecessary
reload of the processes :/

-- 
Alex