You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in networktocode nautobot channel currently backup configs can be seen in the UI only if they were pulled from the devices by the backup job. Backup job is responsible not only for populating the git repository, but also for storing the backup configuration in the DB (which is then used as a source for showing the backup configuration in the UI). At the moment there is no other way how to get the backup configuration into the DB, that way if one uses other means of config backup (rancid, manual, ...) they cannot see the config backup file in the detailed view of golden config page.
Suggestion: "Implement a helper job to populate the DB entry (only syncing the git repository with the DB). Similar to the SyncGoldenConfigWithDynamicGroups job (or it could even be an extension to the that job)."
The text was updated successfully, but these errors were encountered:
https://github.com/nautobot/nautobot-plugin-golden-config/blob/7d1626bb1287c7345cd0102813feb1bbe6a3a52c/nautobot_golden_config/nornir_plays/config_compliance.py#L150
As discussed in networktocode nautobot channel currently backup configs can be seen in the UI only if they were pulled from the devices by the backup job. Backup job is responsible not only for populating the git repository, but also for storing the backup configuration in the DB (which is then used as a source for showing the backup configuration in the UI). At the moment there is no other way how to get the backup configuration into the DB, that way if one uses other means of config backup (rancid, manual, ...) they cannot see the config backup file in the detailed view of golden config page.
Suggestion: "Implement a helper job to populate the DB entry (only syncing the git repository with the DB). Similar to the SyncGoldenConfigWithDynamicGroups job (or it could even be an extension to the that job)."
The text was updated successfully, but these errors were encountered: