Save changes to the master configuration
Use this topic to update the master repository with your console changes, to discard your console changes and continue working with the master repository, or to continue working with your console changes that are not saved to the master repository.
Until you save changes to the master repository, the console uses a local workspace to track your changes.
- Total changed documents
- Timeotal number of documents that you changed for your session, but that are not saved to the master repository. By clicking the +/- toggle key, you can see additional information about the changed documents:
- Changed items
When you change your local configuration, each path and configuration file that you can apply the update to in the master repository is displayed in the list.
- Status
The status can contain the following options:
- Added: If you save your changes to the master repository, a new configuration file is created on the indicated path.
- Updated: If you save your changes to the master repository, an existing configuration file is updated on the indicated path.
- Deleted: If you save your changes to the master repository, an existing configuration file is deleted on the indicated path.
- Synchronize changes with nodes
Specify whether you want to force node synchronization at the time that you save your changes to the master repository, rather than when node synchronization normally occurs.
- Save conflict
Specify that another user changed some configuration information since you began making changes. You can either click Save to overwrite the other user information, or Discard to discard your changes and keep the changes that the other user made.
Related tasks
Start and logging off the console
Related Reference
Administrative console buttons
Reference topic