Skip to content
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

fix: set mysql image version #69

Merged
merged 3 commits into from
May 22, 2024
Merged

fix: set mysql image version #69

merged 3 commits into from
May 22, 2024

Conversation

italopessoa
Copy link
Member

No description provided.

Copy link

coderabbitai bot commented May 22, 2024

Warning

Review failed

The pull request is closed.

Walkthrough

This update integrates a new database project into the solution, refines the README.md with health checking and logging instructions, sets MySQL version to 8.3.0 in the Dockerfile, and adjusts docker-compose.yml dependencies and environment variables for better service integration and logging support.

Changes

Files Change Summary
FIAP.TechChallenge.ByteMeBurger.sln Added a new project named "database" and updated the global section to include the new project reference.
README.md Reordered and added new sections for service health checking and testing; updated service health endpoint URL.
database/Dockerfile Specified MySQL version 8.3.0 and enabled the mysql_native_password option.
docker-compose.yml Removed dependency on seq for the api service; added Serilog__Write__To__2__Args__serverUrl environment variable.

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
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 Configration 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 8ebd6ce and e45aed5.
Files selected for processing (5)
  • FIAP.TechChallenge.ByteMeBurger.sln (2 hunks)
  • README.md (1 hunks)
  • database/Dockerfile (1 hunks)
  • docker-compose.yml (2 hunks)
  • src/FIAP.TechChallenge.ByteMeBurger.Api/Program.cs (2 hunks)
Additional Context Used
LanguageTool (1)
README.md (1)

Near line 45: Possible missing comma found.
Context: ...ase with fake data and test some of the endpoints use the [FIAP_TechChallenge_ByteMeBurge...

Markdownlint (12)
README.md (12)

17: Expected: 1; Actual: 2
Multiple consecutive blank lines


35: Expected: 1; Actual: 2
Multiple consecutive blank lines


39: Expected: 1; Actual: 2
Multiple consecutive blank lines


53: Expected: 1; Actual: 2
Multiple consecutive blank lines


5: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


8: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


10: Expected: 1; Actual: 0; Above
Headings should be surrounded by blank lines


12: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


18: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


20: null
Fenced code blocks should be surrounded by blank lines


13: null
Lists should be surrounded by blank lines


19: null
Lists should be surrounded by blank lines

Path-based Instructions (1)
src/FIAP.TechChallenge.ByteMeBurger.Api/Program.cs (1)

Pattern **/*.cs: Validate all files and structures against Domain Driven Design principles and Ports & Adapters architecture pattern.

Additional comments not posted (5)
database/Dockerfile (1)

2-2: Ensure MySQL version 8.3.0 is compatible with other project dependencies.

docker-compose.yml (1)

36-36: Updated service tag aligns with project naming conventions.

README.md (1)

37-37: Updated health check URL reflects the new endpoint.

src/FIAP.TechChallenge.ByteMeBurger.Api/Program.cs (1)

98-98: Updated health check endpoint path to /healthz aligns with standard practices.

FIAP.TechChallenge.ByteMeBurger.sln (1)

59-64: Addition of the new database project to the solution file.


# NOTE: use of "mysql_native_password" is not recommended: https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password
# (this is just an example, not intended to be a production configuration)
CMD ["mysqld", "--mysql-native-password=ON"]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider the security implications of using mysql_native_password.

It's recommended to use more secure authentication methods than mysql_native_password, especially for production environments. Consider alternatives such as caching_sha2_password.

@@ -27,16 +26,14 @@
- MySqlSettings__UserId=${MYSQL_USERID}
- MySqlSettings__Password=${MYSQL_PASSWORD}
- ASPNETCORE_ENVIRONMENT=Development
- Serilog__Write__To__2__Args__serverUr=http://seq:5341
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct the typo in the Serilog server URL.

- Serilog__Write__To__2__Args__serverUr=http://seq:5341
+ Serilog__Write__To__2__Args__serverUrl=http://seq:5341

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
- Serilog__Write__To__2__Args__serverUr=http://seq:5341
- Serilog__Write__To__2__Args__serverUrl=http://seq:5341

README.md Outdated
> [http://localhost:8080/healthz](http://localhost:8080/healthz)


5. Testing
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a comma for clarity in the testing section.

- To verify the existing endpoints go to
+ To verify the existing endpoints, go to

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
5. Testing
5. Testing
To verify the existing endpoints, go to

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 e45aed5 and fbe4c05.
Files selected for processing (1)
  • docker-compose.yml (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • docker-compose.yml

@italopessoa italopessoa merged commit 2f462c3 into main May 22, 2024
@italopessoa italopessoa deleted the fix_docker_mysql_version branch May 22, 2024 16:35
@italopessoa italopessoa added the Phase 2 Kubernetes Management label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Phase 2 Kubernetes Management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant