Configsets
Gatekeeper is configured using different parameters, gathered into configsets. A configset is a collection of configuration parameters identified by a name that is unique within the scope (insensitive casing). The main purpose of a configset is to group parameters into a set that is tuned for a specific usage scenario. This has the advantage of separating integration and tuning activities: users do not need to determine the best parameter values during the design phase of a project.
Instead, the initial application can reference the names of different configsets for different purposes and determine the final parameter values later (as part of testing, tuning, deployment, and so on).
Every configset is associated with a context (or description). This is a free-text field that describes the purpose and usage of the configset. Gatekeeper can use the field for any purpose whatsoever. Because the context tag appears in the system audit trail, users can examine audits to discover what was happening at any moment in time.
There can be multiple configsets with the same name and different states (such as saved, validated, inactive), but there can only be one active configset per name.
Configset revisions are immutable, so every change effectively creates a new revision.
You can add metadata to a configset including date and time of creation, name of the user that created the configset, and more.
Configset templates
A configset template is a special type of configset with custom values tuned to support a specific use case. The purpose of a template is to speed the creation of new configsets for common scenarios while ensuring that parameters are set optimally.
Each template contains parameters and values for the target usage scenario. Other parameters retain their default values. Although this documentation describes default values, the actual value might be different when you use a template to create a new configset.