cnitool actually requires you to use the .conflist extension, with .conf you get errors.
-----Original Message----- Subject: RE: Is it not time the cni configuration dir loads only specific extensions? Hi Benjamin, Qian, I am just trying to stress that this is not default behaviour and thus not expected. Major implementations like apache httpd and sysctl are ignoring other extensions. To me it is irrelevant if this currently documented or not, or easy to adapt to. One should follow 'standards' as much as possible. -----Original Message----- Subject: Re: Is it not time the cni configuration dir loads only specific extensions? Hi Marc, I guess Qian was confused by your email body containing no question. To answer the question from the email’s subject: > Is it not time the cni configuration dir loads only specific extensions? I would say, no, it is not. The current behavior is documented, pretty simple for both users and implementors (e.g., no need to handle multiple possible extensions), and not unusual since a non-vanishing number of tools would also try to load all files from a specific directory. Additionally, changing what files would be considered would be a breaking change for little benefit. Cheers, Benjamin
