DOCSEARCHbyAlgolia
Submit Docs

Fig Settings Documentation

website·Indexed 30 days ago

https://www.figsettings.com

A complete solution for managing settings and configuration across multiple micro-services. Fig provides secure client secret management with providers for AWS, Azure, Google, Docker, and Windows DPAPI, as well as integration points for lookup tables and webhooks. Supports versions 2.0, 3.x, and Next, including an MCP Server for AI tools like GitHub Copilot CLI, Claude Desktop, and Cursor.

Tokens
438.2K
Snippets
1.8K
Records
3.1K
Agent score
34%

What's inside Fig

  1. Overview of Fig as a Configuration Provider

    Fig is a complete configuration management solution for .NET micro-services. Unlike standard configuration providers, Fig allows applications to register their configuration upon startup, making those settings viewable and editable via a dedicated web application. It can operate alongside other configuration sources.

  2. Overview of Fig Setting Groups

    Setting groups in Fig allow you to link related settings from multiple clients so they can be organized and managed together. This is particularly useful for shared configurations, such as database connection strings used across multiple microservices. Groups are managed via the web application and do not require code changes after the initial setup.

  3. Overview of Fig security features

    Fig v4.x implements several security measures to protect settings and user data:

    • Encryption: All setting values are encrypted in the database using the server secret. Offline settings files are encrypted using client secrets.
    • Access Control: The web application is protected by credentials; clients must use their secret to access settings. User roles restrict access to setting and history information (excluding user activity).
    • Password Policy: Fig uses the zxcvbn password-strength estimator to enforce 'good' passwords and provides real-time suggestions/warnings.
    • Data Privacy: Secret setting values are never transmitted to the Fig Web Application.
    • Administrative Controls: Admins can force password changes on next login, disable file imports, and disable new setting registrations.
    • Audit: All actions are logged and recorded in the database.

  4. Overview of Fig Sentinel Connector features

    The Fig Sentinel Connector (v3.x) is an experimental integration that forwards Fig webhook events to Microsoft Sentinel for Security Information and Event Management (SIEM) monitoring. Key capabilities include:

    • Security Event Monitoring: Forwards login attempts and user creation events.
    • Configuration Change Tracking: Monitors setting value changes across applications.
    • Client Health Monitoring: Tracks client registrations, status changes, and health events.
    • Event Filtering: Configurable processing of specific event types.
    • Reliability: Built-in retry logic with exponential backoff and health checks for the Sentinel connection.

  5. Overview of Fig Sentinel Connector features

    The Fig Sentinel Connector is an experimental integration that forwards Fig webhook events to Microsoft Sentinel for Security Information and Event Management (SIEM) monitoring. Key capabilities include:

    • Security Event Monitoring: Forwards login attempts and user creation events.
    • Configuration Change Tracking: Monitors setting value changes across applications.
    • Client Health Monitoring: Tracks client registrations, status changes, and health events.
    • Event Filtering: Allows selection of specific event types to process.
    • Reliability: Includes built-in retry logic with exponential backoff and health checks for the Sentinel connection.

  6. Overview of Fig Sentinel Connector features

    The Fig Sentinel Connector (v4.x) is an experimental integration that forwards Fig webhook events to Microsoft Sentinel for Security Information and Event Management (SIEM) monitoring. Key capabilities include:

    • Security Event Monitoring: Forwards login attempts and user creation events.
    • Configuration Change Tracking: Monitors setting value changes across applications.
    • Client Health Monitoring: Tracks client registrations, status changes, and health events.
    • Event Filtering: Allows selection of specific event types to process.
    • Reliability: Includes built-in retry logic with exponential backoff and health checks for the Sentinel connection.

  7. Overview of Fig Setting Groups

    Setting groups in Fig allow you to link related settings from multiple clients to organize and manage them together. For example, multiple microservices sharing a database connection string can be grouped so the relationship is visible and maintainable in one place. Groups are managed via the web application and do not require code changes after initial setup.

  8. Overview of Fig configuration management for .NET

    Fig is a configuration provider for .NET (compatible with .NET Core's IOptions<T> pattern) designed to manage settings across multiple microservices. It addresses common shortcomings of local files like appsettings.json by providing:

    • Centralized management of settings across multiple applications.
    • Sharing of settings between applications.
    • Audit logging for configuration changes.
    • A web client for updating and managing settings.
    • Type-safe settings editors and text descriptions to prevent configuration errors.

    Fig integrates into the existing configuration provider pipeline, allowing it to be used alongside other providers. Settings are registered with the Fig API during application startup and can be managed via the Fig web client.

  9. Overview of Fig Dashboards

    Dashboards are read-only, configurable views of Fig status and settings data, typically used for wallboards, operations boards, and fleet health summaries. They utilize a 12-column grid layout and trusted Fig UI components. Data is bound to components using inline JavaScript scripts (executed via Jint) that transform live data from the fig object into the format required by the component. Note that users cannot inject HTML or Razor; only data transformations are permitted.

  10. Overview of Fig Setting Groups

    Setting groups in Fig allow you to link related settings from multiple clients to organize and manage them together. For example, multiple microservices sharing a database connection string can be grouped so the relationship is visible and maintained in one place. Groups are managed via the web application and do not require code changes after the initial setup.

  11. Overview of Fig Setting Groups

    Setting groups in Fig allow you to link related settings from multiple clients so they can be organized and managed together. This is particularly useful for shared configurations, such as a database connection string used across several microservices. Groups are managed via the web application and do not require code changes for modification or deletion after the initial setup.

  12. Overview of Fig settings-management architecture

    Fig is a centralized settings-management system designed for .NET services. It allows operators to manage configuration values via a web interface (Fig Web), while applications consume these settings through the standard ASP.NET configuration system using IOptions and IOptionsMonitor. To ensure high availability and resilience, multiple API instances can share a single database, and clients maintain an encrypted local cache to allow applications to start even if the API is temporarily unreachable.