-
Notifications
You must be signed in to change notification settings - Fork 7
BSL CFG Requirements
ckrup edited this page Jan 16, 2025
·
2 revisions
| Rqmt ID | Title | Description | Rationale | Verification |
|---|---|---|---|---|
| BSL-CFG-1-0 | Runtime Configuration | The BSL shall establish a catalog of settings that users may configure at run-time. | Settings configuring runtime settings, such as max blocks per bundle, max extension block size, max concurrent security operations, and memory/disk space allocations. | Test |
| BSL-CFG-2-0 | Setting Configuration Items | The BSL shall allow parameterization via configuration files and environment variables. | Different deployments may favor certain mechanisms for setting the configuration. The BSL should identify the relative prioritization among them. | Test |
| BSL-CFG-3-0 | Showing Build Information | The BSL shall embed build information into runtime artifacts | Helps system administrators or other users confirm the build revision and its build settings. | Test |
| BSL-CFG-4-0 | Version Identification | The BSL shall embed version into the executable, and be identified when running the application. | This is used to provide insight into the BSL version for users. | Test |
| BSL-CFG-5-0 | Compile-time Configuration | The BSL shall provide a catalog of configurable compile-time items. | This may include items such as debug mode, telemetry or logging libraries. | Test |
| BSL-CFG-6-0 | Run-time Configuration | The BSL shall provide a catalog of configurable run-time items. | This may include items such as “maximum bundle size”, “max concurrent transactions”, and timeouts and watchdog values. | Test |
| BSL-CFG-7-0 | Command-line Configuration | The BSL shall support parameterization by compiler command line arguments and configuration files. | Configuration items may be given either through the command-line or in configuration file, not both. | Test |