-
Notifications
You must be signed in to change notification settings - Fork 9
Resync cloned repository
araman-m edited this page Feb 15, 2023
·
1 revision
to resync your cloned repository after main repository was updated
- go into your cloned repository, make sure you reload page if necessary
- if they are a changes, you will see a resync repository with added and removed stuff (especially if you changed topology from default)
- clic on "Sync Changes"
- Depending on the changes made upfront, that may do a full resync , this is expected but the Github action will automaticallly run after resync and move files again to match topology targeted (as your variable stay local) If that double run happen, you will have a commit starting with TOPOLOGY change. if you run in VCS mode , make sure to discard the first run and only apply the second one that include TOPOLOGY (which the commit message will tell you to do)
- Home
- Backups
- Local-backups
- Customizing-backup-settings
- Externalizing-backups
- splunkconf‐backup-cost-optimisation-with-tag-and-frequency
- Remote-Mounted-FS
- Setting-up-ssh-keys-for-rsync-rcp-modes
- Remote-backup-via-RCP-on-remote-directory
- Rsync-over-SSH-for-DRP-purpose-between-2-Splunk-hosts
- Backups-logs
- Debugging-backups
- Know-issues
- Restoring-backups
link to repository link to splunkbase app