configcat

ConfigCat feature flag management is handled by running bundled bash scripts that route operations like inspect, add, update, and delete through the Management API. Scripts load credentials from a .env file and safely handle reads and writes.

Before inspecting ConfigCat environments and settings, you must configure credentials in a sibling .env file. The toolkit requires curl, jq, rg, and base64 dependencies to execute dispatcher scripts and Management API requests.

Yes, you can update feature flag values across dev and prod workflows using bash scripts. The toolkit covers products, configs, environments, and settings, enabling modification and troubleshooting across workflows via the Management API.

ConfigCat Management API keeps runtime evaluation separate from flag inspection by routing dispatcher scripts exclusively for management tasks like reading and writing settings. This ensures runtime flag evaluation remains independent of inspection operations.

The best way to troubleshoot ConfigCat flag lifecycle changes is to use the provided reference docs and bundled scripts in the references directory. They guide inspection of products, configs, and environments to identify issues during modification.

ConfigCat bash scripts fail to load credentials when the .env file is missing or incorrectly placed. The toolkit enforces credential handling by loading secrets from a sibling .env file, which must be properly configured before executing operations.