🗃️ Settings Management
19 items
📄️ Verifications
Fig includes a framework for verifying setting values from within the UI. The setting verifications occur within the Fig API.
📄️ Event History
Everything that occurs within Fig is logged in the database and is available in the event history.
📄️ User Management
Administrators in the Fig web client have the ability to manage users. They are able to create and delete users (or other administrators) as well as set and reset passwords.
📄️ Import / Export
Fig supports a number of different types of import and export.
📄️ Lookup Tables
Fig supports the concept of lookup tables. This is where a set of setting values supplied by a client can be translated into more user friendly values.
📄️ Configuration
There are a few parameters which can be configured for Fig which enable or disable certain features in the application.
📄️ Client Management
Administrators in Fig are able to see a list of all currently connected clients. Clients are considered connected if they poll the API at least once every 2 times the configured poll interval for that client. Clients will poll automatically as part of the Fig.Client nuget package and deault to 30 seconds per poll.
📄️ API Management
The Fig API is stateless and as a result, it is possible to run multiple instances of the API pointing towards the same database.
📄️ Offline Settings
By default, clients using the Fig.Client nuget package will support offline settings. This is a fallback mechanism for when the Fig.API is offline. If the client application starts and it is unable to contact the API, it will attempt to load the last values that it got from the API and run with those. It will continue to attempt to contact the API and will update the settings once successfully reconnected.
📄️ Live Reload
By default, clients using the Fig.Client nuget package will support the live reload of settings. This means that when a setting value is updated in the Web Client, that updated value will immediately be available in the settings class for that client. In addition, a settings changed event will be raised on the settings class which can be used to take action when it occurs.
📄️ Authentication
Fig has built in authentication to protect your settings. Access to the Fig web application is protected by a username and password.
📄️ Instances
Fig supports overriding the default settings for a client with an instance. An instance is a special key that can be passed by the calling client. When an instance is provided, Fig attempts to find settings matching that instance name. If none are found, the default settings for that client are returned.
📄️ Web Hooks
Fig has a web hook integration point which allows third party integrations to be called by Fig in response to certain events occurring. This allows events from Fig to be available more widely for example sent to someone via email or posted to a Slack or Teams channel.
📄️ Compact View
When there are lots of settings for a client or settings have large descriptions it can be difficult to get an overview of the settings and their values. This is where compact view can be useful. An individual setting can have their compact view toggled by clicking on the name. All settings under a client can be collapsed or expanded using the command buttons at the top of the settings.
📄️ Memory Leak Detection
Fig has built in memory leak detection. Clients with suspected memory leaks will be shown in the insights page and web hooks can be sent once a possible leak is detected.
📄️ Client Descriptions
When configuring many different clients, having a description of that application and what it does can be useful to the person performing the configuration. Fig forces developers to enter a value in for the client description when they start using Fig and this description is then available when performing the configuration.
📄️ Settings Table
All settings can be reviewed in table format which includes when the settings where last. This can be useful when trying to search for specific settings or review recent changes in an easy to review format. All columns can be filtered or sorted as required.
📄️ Change Message
When you save settings changes, you will be prompted to enter a change message. This message will be stored in the event log along with the value changes. It can be a good way to record the motivation behind the change.
📄️ Client Settings Overrides
In some situations you want the settings to be driven by the client. For example when deploying applications using Docker compose if you have address to other containers within the compose file, you can reference them by their container name. In that case, you would like the setting to be set by the docker compose file rather than having to be manually set in Fig or use a default.
📄️ Azure Key Vault Integration
Fig can handle secret values with all setting values being stored encrypted in an enterprise database. However for some high security deployments it may be desirable to store secret values in a dedicated secret store such as Azure Key Vault. Fig has an integration to Azure Key Vault and if enabled, all values marked as secret attribute will be stored there rather than the fig database.
📄️ App.config File Generation
Fig integrates into the configuration framework built into ASP.NET core. As part of that framework it is possible to draw configuration from a variety of sources including appSettings.json files, environment variables and app.config files. App.config files are largely legacy but are sometimes required for backwards compatibility. They can be tricky to write so they are compatible with the nested structure of the appSettings.json files.
📄️ Keyboard Shortcuts
The fig web application supports keyboard shortcuts for common operations.