adjustments to sudo call and log test

[veggiesaurus]

Closes #97

@confluence do you think we need to warn users about the additional line in the sudoers file that is now needed?

[confluence]

I think that there should be some kind of warning. This may be a good time to add a changelog, so that it can be included in the package metadata. We should probably also add the changelog to the documentation.

Is there any way for an npm package to print messages for the user upon installation?

[confluence]

I wonder if a safer option would be 1) to give the user explicit control over the sudo arguments as well as the sudoers config, and 2) leave the previous setup as the default. This would make upgrades safe, and also makes sense because we're compensating for an old version of sudo rather than changing to accommodate a new version.

If we did that, we could just add a note to the extended configuration explaining what to do with an older version of sudo.

We could also automatically detect the sudo version and pick the correct arguments (instead of exposing this to the user).

[veggiesaurus]

I wonder if a safer option would be 1) to give the user explicit control over the sudo arguments as well as the sudoers config, and 2) leave the previous setup as the default. This would make upgrades safe, and also makes sense because we're compensating for an old version of sudo rather than changing to accommodate a new version.

That's a good point. I've actually just tried bionic and centos7/8 docker images, and they all seem to have a new enough sudo version, so I suspect this is related to RHEL7 in particular.

[veggiesaurus]

@confluence I have now added the config option you suggested, please re-evaluate