Add CLI parameter for data-source.health.name #3059
Draft
+128
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why make this change?
The
data-source.health.nameproperty exists in the DAB schema but was not exposed as a CLI parameter, making it impossible to configure via command line.What is this change?
Added
--data-source.health.nameCLI parameter to thedab configurecommand.Implementation details:
DataSourceHealthNameparameter toConfigureOptionswith CLI option bindingTryUpdateConfiguredDataSourceOptionsto create or update health configuration while preserving existing settingsDatasourceHealthOptionsConvertorFactory.Write()to serialize health object when name is set (previously only serialized when enabled was explicitly provided)How was this tested?
TestAddDataSourceHealthName- validates adding name to config without health sectionTestUpdateDataSourceHealthName- validates updating name while preserving existing health settingsSample Request(s)
CLI usage:
Result:
{ "data-source": { "database-type": "mssql", "connection-string": "@env('MSSQL_CONNECTION_STRING')", "health": { "enabled": true, "name": "Production SQL Server" } } }Original prompt
dab configure --data-source.health.nameis missing. #3058💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.