ExecuteQueryToFile - add managed identity authentication

[FrendsSarlinS]

Closes #46. Microsoft.Sql -namespace declared and used instead of System.Data.SqlClient as per instructions. 2.0.0 change.

Summary by CodeRabbit

• New Features

  • Upgraded to version 2.0.0, featuring a transition to the Microsoft.Data.SqlClient library for improved performance and capabilities.
  • Enhanced connection security with the addition of TrustServerCertificate=True in connection strings.

• Bug Fixes

  • Improved handling of null query parameters in previous versions.

• Documentation

  • Changelog updated to reflect the significant changes and enhancements in version 2.0.0.

• Chores

  • Updated project configuration to remove the older System.Data.SqlClient reference and include Microsoft.Data.SqlClient.

[coderabbitai]

Walkthrough

The recent update to Frends.MicrosoftSQL.ExecuteQueryToFile includes a significant transition from System.Data.SqlClient to Microsoft.Data.SqlClient, enhancing compatibility with modern features and capabilities. This change necessitates a review of existing implementations due to potential breaking changes. Additionally, the version has been incremented to 2.0.0, reflecting these major updates.

Changes

Files	Change Summary
Frends.MicrosoftSQL.ExecuteQueryToFile/CHANGELOG.md	Updated changelog to reflect changes in version 2.0.0, highlighting the transition to Microsoft.Data.SqlClient and its implications.
Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/UnitTests.cs	Updated unit tests to utilize Microsoft.Data.SqlClient for SQL parameter instantiation.
Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/lib/Helper.cs	Changed SQL parameter definitions to use Microsoft.Data.SqlClient in the InsertTestData method. Updated connection string to include TrustServerCertificate=True.
Frends.MicrosoftSQL.ExecuteQueryToFile/Definitions/CsvFileWriter.cs	Replaced System.Data.SqlClient with Microsoft.Data.SqlClient in import statements.
Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.cs	Modified import statements to use Microsoft.Data.SqlClient.
Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.csproj	Updated project version to 2.0.0 and added Microsoft.Data.SqlClient package reference.

Assessment against linked issues

Objective	Addressed	Explanation
Add managed identity authentication (Issue #46)	❌	No changes related to managed identity were made.

🐰 In the land of code, where changes thrive,
A new SQL client helps us jive!
With modern features, we leap and bound,
In version two, new joys abound!
So hop along, let’s give a cheer,
For smoother queries, we hold dear! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b2e97c7 and 1a22a03.

Files selected for processing (6)

• Frends.MicrosoftSQL.ExecuteQueryToFile/CHANGELOG.md (1 hunks)
• Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/UnitTests.cs (2 hunks)
• Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/lib/Helper.cs (2 hunks)
• Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile/Definitions/CsvFileWriter.cs (2 hunks)
• Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.cs (1 hunks)
• Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.csproj (2 hunks)

Additional comments not posted (10)

Frends.MicrosoftSQL.ExecuteQueryToFile/CHANGELOG.md (2)

3-3: LGTM!

The versioning and date format are consistent with standard practices.

---

5-5: LGTM!

The breaking change is clearly described and provides necessary information.

Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/lib/Helper.cs (2)

4-4: LGTM!

The import statement is correctly updated to use Microsoft.Data.SqlClient.

---

25-25: LGTM!

The method signature is correctly updated to use Microsoft.Data.SqlClient.SqlParameter.

Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.csproj (2)

6-6: LGTM!

The version update to 2.0.0 is consistent with the breaking changes introduced.

---

33-33: LGTM!

The package reference to Microsoft.Data.SqlClient version 5.2.1 is correctly added.

Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.cs (1)

10-10: Update import statement to use Microsoft.Data.SqlClient.

The import statement has been updated to use Microsoft.Data.SqlClient, which is a newer and more feature-rich library compared to System.Data.SqlClient. Ensure that all usages of the SQL client in this file are compatible with the new library.

Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile/Definitions/CsvFileWriter.cs (1)

14-14: Update import statement to use Microsoft.Data.SqlClient.

The import statement has been updated to use Microsoft.Data.SqlClient, which is a newer and more feature-rich library compared to System.Data.SqlClient. Ensure that all usages of the SQL client in this file are compatible with the new library.

Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/UnitTests.cs (2)

9-9: Update import statement to use Microsoft.Data.SqlClient.

The import statement has been updated to use Microsoft.Data.SqlClient, which is a newer and more feature-rich library compared to System.Data.SqlClient. Ensure that all usages of the SQL client in this file are compatible with the new library.

---

58-64: Update SqlParameter instantiation to use Microsoft.Data.SqlClient.

The instantiation of SqlParameter objects has been updated to use Microsoft.Data.SqlClient. Ensure that the new SqlParameter objects are correctly instantiated and compatible with the new library.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1a22a03 and e5ae5ab.

Files selected for processing (1)

• Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/lib/Helper.cs (2 hunks)

Additional comments not posted (3)

Frends.MicrosoftSQL.ExecuteQueryToFile/Frends.MicrosoftSQL.ExecuteQueryToFile.Tests/lib/Helper.cs (3)

4-4: LGTM! Transition to Microsoft.Data.SqlClient.

The change from System.Data.SqlClient to Microsoft.Data.SqlClient is appropriate for the 2.0.0 update.

---

12-12: Verify the necessity of TrustServerCertificate=True.

Including TrustServerCertificate=True can introduce security risks in production environments. Ensure that this parameter is necessary and consider its implications.

---

25-25: LGTM! Transition to Microsoft.Data.SqlClient.SqlParameter.

The change from System.Data.SqlClient.SqlParameter to Microsoft.Data.SqlClient.SqlParameter is appropriate for the 2.0.0 update.