-
-
Notifications
You must be signed in to change notification settings - Fork 3
Ver 600 #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ver 600 #106
Conversation
Updated Roslynator.Analyzers to 4.12.9 and Scrutor to 5.0.1. Enhanced JwtOptions with XML docs and new default values. Refactored RabbitMQ config in ServiceCollectionExtensions. Added JWT settings to appsettings.json and disabled azureKeyVault. Updated various Microsoft.Extensions packages in Genocs.Core.csproj. Tested to use auth with simmetric key.
Updated project references in various .csproj files to use newer versions of dependencies. Removed `netstandard2.1` from target frameworks in `Genocs.Common.csproj` and `Genocs.Core.csproj`. Changed primary key type from `int` to `Guid` for several domain entities and interfaces. Improved documentation comments and exception handling. Made `Id` property non-nullable in `Entity` class. Added `net8.0` target framework to `Genocs.SignalR.WebApi.csproj` and reorganized `Content` item group for certificates.
Updated project versions to 6.2.0 and replaced Jaeger tracing with OpenTelemetry across various projects. Enhanced Swagger configuration, improved null safety with nullable reference types, and refactored code for better readability and maintainability. Removed unnecessary metadata from project files and updated package references to specific versions.
Updated Directory.Build.props to use Roslynator.Analyzers 4.12.9. Removed net8.0 and net7.0 FrameworkReferences from Genocs.Core.csproj. Now, Microsoft.AspNetCore.App is referenced only for net6.0.
Updated `Directory.Build.props` to include additional files for packaging. Removed these files from multiple `.csproj` files. Updated `Genocs.Core.Demo.WebApi.csproj` and `Genocs.Core.Demo.Worker.csproj` to reference `MassTransit.RabbitMQ` v8.3.0. Updated `Genocs.Secrets.AzureKeyVault.csproj` to reference `Azure.Identity` v1.13.1. Added new package references for Release configuration in `Genocs.APIGateway.csproj` and `Genocs.Orders.WebApi.csproj`.
Updated various Genocs package references from version 6.2.0 to 6.3.0 across multiple project files. This includes updates to `Genocs.Core`, `Genocs.QueryBuilder`, `Genocs.Persistence.MongoDb`, `Genocs.MessageBrokers.RabbitMQ`, `Genocs.Tracing`, `Genocs.WebApi`, and other related packages. Removed redundant `<Version>6.2.0</Version>` tags from several project files to streamline version management.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 13626644 | Triggered | Generic Password | ee78547 | containers/infrastructure-oracle.yml | View secret |
| 13626644 | Triggered | Generic Password | ee78547 | containers/infrastructure-mysql.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 secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
No description provided.