Add Serialization & Deserialization of Sink File Properties with CLI Commands

[RubenCerna2079]

Why make this change?

This change solves issue #2749.

What is this change?

CLI Commands Added

The following new CLI configure options are now available:

--runtime.telemetry.file.enabled - Enable/disable file sink telemetry (default: false)
--runtime.telemetry.file.path - File path for telemetry logs (default: "/logs/dab-log.txt")
--runtime.telemetry.file.rolling-interval - Rolling interval: hour, day, week (default: day)
--runtime.telemetry.file.retained-file-count-limit - Number of retained files (default: 1, minimum: 1)
--runtime.telemetry.file.file-size-limit-bytes - Max file size in bytes (default: 1048576, minimum: 1)

JSON Configuration Schema

The configuration now supports the following structure under runtime.telemetry:

{
  "runtime": {
    "telemetry": {
      "file": {
        "enabled": true,
        "path": "/logs/dab-log.txt",
        "rolling-interval": "day",
        "retained-file-count-limit": 7,
        "file-size-limit-bytes": 1048576
      }
    }
  }
}

How was this tested?

• Integration Tests
• Unit Tests
• Manual Tests

Sample Request(s)

• Example REST and/or GraphQL request to demonstrate modifications
• Example of CLI usage to demonstrate modifications

[Copilot]

Pull Request Overview

This PR adds support for file-based telemetry sinks by extending configuration, CLI commands, and JSON schema.

• Introduces a new FileSinkOptions model and RollingIntervalMode enum.
• Updates TelemetryOptions and ConfigGenerator to incorporate file sink settings.
• Expands the CLI (AddTelemetryOptions, ConfigureOptions) and adds unit tests and JSON schema entries for file sink parameters.

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/Config/ObjectModel/FileSinkOptions.cs	New record for configuring file sink telemetry.
src/Config/ObjectModel/FileSinkRollingIntervalMode.cs	New enum for file sink rolling intervals.
src/Config/ObjectModel/TelemetryOptions.cs	Extended to include File property.
src/Cli/ConfigGenerator.cs	Wired file sink options into runtime config builder.
src/Cli/Commands/AddTelemetryOptions.cs	Added CLI flags for file sink telemetry settings.
src/Cli/Commands/ConfigureOptions.cs	Exposed file sink flags on dab configure command.
src/Cli.Tests/ConfigureOptionsTests.cs	Added tests for file sink CLI configuration.
schemas/dab.draft.schema.json	Added JSON schema for file sink under runtime.telemetry.file.
src/Cli/Properties/launchSettings.json	Updated default CLI launch arguments for testing.

Comments suppressed due to low confidence (1)

src/Cli.Tests/ConfigureOptionsTests.cs:886

• The tests reference RollingInterval, but the enum is named RollingIntervalMode. Update references to RollingIntervalMode.Hour (and similarly for Day/Week).

        [DataRow(RollingInterval.Hour, DisplayName = "Update rolling interval to Hour.")]

[Copilot]

The default JsonStringEnumConverter will serialize enum values as "Hour"/"Day"/"Week", but the JSON schema expects lowercase strings ("hour","day","week"). Consider using JsonStringEnumConverter with a camel‐case naming policy (e.g. new JsonStringEnumConverter(JsonNamingPolicy.CamelCase)) or adjust the schema to match.

Suggested change

	[JsonConverter(typeof(JsonStringEnumConverter))]
	[JsonConverter(typeof(JsonStringEnumConverter), JsonNamingPolicy.CamelCase)]

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[aaronburtle]

For any of these properties with defaults, if the default value is being used, but was not supplied by the user, does the property end up writing back out to the config?

[aaronburtle]

if we try to make FileSinkOptions with values below the minimum in the schema, do we end up with an invalid config, or do we error out first?

[aaronburtle]

Can we add some kind of a test to validate the scenario?