nautobot/nautobot-app-golden-config

Compliance checks without intended / backup configuration

viktorkertesz opened this issue · 1 comments

Environment

  • Nautobot version: 1.6.10
  • nautobot-golden-config version: 1.6.2

We don't maintain backup nor full intended configuration for an isolated environment. Therefore running
compliance checks are impossible without hacks.

Proposed Functionality

Can we set an option at compliance job not to check if a device have intended or backup configuration?
In those cases, ignore git operation and also let the check run with custom compliance function.

Use Case

Our use case is that we don't rely on configuration directly but we use custom compliance function which works on device custom field data. Creating dummy data for intended and backup is ugly.

It may benefit others using similar compliance strategy.

Perhaps a "faker" job, that generates the files for you that are all empty. This would still require you to have a git instance, but I think that is a reasonable in between as to handle this use case would likely result in a lot of extra conditional code.