Azure / Azure/data-api-builder

[Bug]: ConnectionString parsing for AppInsights - DAB CLI

Open
#2,046 2 comments 0 reactions 1 assignee Claimed by @abhishekkumams View on GitHub
bug cli
Dominant language
C#
Stars
1.5k
Forks
370
Avg merge
3d 17h
Merged PRs (30d)
8

Description

### What happened?

A bug happened!

Invalid connection string results in uncaught exception.

When starting using "dab start" the error message returned when connection string is invalid is not user-friendly. See stack trace. I originally thought the error was for db connection string until i saw stack trace originated from "Microsoft.ApplicationInsights"

### Version

.11rc

### What database are you using?

Azure SQL

### What hosting model are you using?

Local (including CLI)

### Which API approach are you accessing DAB through?

REST

### Relevant log output

```Text

crit: Microsoft.AspNetCore.Hosting.Diagnostics[6]
Application startup exception
System.ArgumentException: There was an error parsing the Connection String: Input contains invalid delimiters and cannot be parsed. Expected example: 'key1=value1;key2=value2;key3=value3'.
---> System.ArgumentException: Input contains invalid delimiters and cannot be parsed. Expected example: 'key1=value1;key2=value2;key3=value3'.
at Microsoft.ApplicationInsights.Extensibility.Implementation.ConfigString.ConfigStringParser.Parse(String configString)
```

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.