Upgrade to .Net 8 - #604
Draft
mozts2005 wants to merge 20 commits into
Draft
Conversation
- Updated all projects to target .NET 8.0 - Upgraded NuGet packages for .NET 8 compatibility (Newtonsoft.Json, Microsoft.Extensions.Configuration.*) - Adjusted code and pipeline for new ZendeskApi auth signature (API token) - Validated WebRequest API compatibility; no code changes needed - Marked user segment CRUD tests as ignored (TODO) - Added detailed progress and execution logs for upgrade tasks - All upgrade tasks complete; solution builds and tests pass on .NET 8 Upgrade to .NET 8, refactor auth, update dependencies Upgraded all projects to .NET 8.0 and updated package references for compatibility, including Newtonsoft.Json and Microsoft.Extensions.Configuration. Refactored ZendeskApi usage to use API token authentication instead of passwords. Updated Azure Pipelines to reflect password deprecation. Marked some user segment tests as ignored and improved assertions. Removed obsolete target framework property groups.
- Updated all projects to target .NET 8.0 - Upgraded NuGet packages for .NET 8 compatibility (Newtonsoft.Json, Microsoft.Extensions.Configuration.*) - Adjusted code and pipeline for new ZendeskApi auth signature (API token) - Validated WebRequest API compatibility; no code changes needed - Marked user segment CRUD tests as ignored (TODO) - Added detailed progress and execution logs for upgrade tasks - All upgrade tasks complete; solution builds and tests pass on .NET 8 Upgrade to .NET 8, refactor auth, update dependencies Upgraded all projects to .NET 8.0 and updated package references for compatibility, including Newtonsoft.Json and Microsoft.Extensions.Configuration. Refactored ZendeskApi usage to use API token authentication instead of passwords. Updated Azure Pipelines to reflect password deprecation. Marked some user segment tests as ignored and improved assertions. Removed obsolete target framework property groups.
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
…skApi_v2 into upgrade-to-NET8
… DevOps pipeline - Added CI and Release workflow for building, testing, and publishing packages. - Introduced Deploy Infrastructure workflow for managing Azure resources. - Updated README with CI/CD documentation and moved related content to `docs/ci-cd.md`. - Created infrastructure documentation in `infra/README.md`. - Disabled legacy Azure DevOps pipeline and retained it for historical reference. - Added parameters and modules for Azure Artifact Signing in Bicep files. - Documented Azure signing resource cleanup process.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 33991333 | Triggered | Generic Password | 8755d68 | .github/workflows/ci-release.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR Classification
Upgrade and refactor for .NET 8.0 compatibility and improved authentication.
PR Summary
This pull request upgrades the solution to .NET 8.0, updates dependencies, and switches ZendeskApi authentication to use API tokens. It also adjusts tests and CI configuration accordingly.