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: adjust uploads path regex to support trailing slashes #57

Merged
merged 5 commits into from
Nov 25, 2024

Conversation

akshat5302
Copy link
Collaborator

@akshat5302 akshat5302 commented Oct 16, 2024

update uploads path regex to allow trailing slash (/uploads, /uploads/)

Summary by CodeRabbit

  • New Features

    • Enhanced application configuration with new entries for Sentry, debugging, and environment variables.
    • Improved routing for the MinIO service in the ingress configuration, including a new GraphQL endpoint.
  • Version Updates

    • Updated application version from 1.0.12 to 1.1.0.

Copy link

coderabbitai bot commented Oct 16, 2024

Walkthrough

The changes in this pull request involve updates to Kubernetes configuration files for the plane-ce and plane-enterprise applications. The app-env.yaml file sees enhancements to a Secret and a ConfigMap, adding multiple new data entries for configuration flexibility. The Chart.yaml file has its version incremented from 1.0.12 to 1.1.0. Additionally, the ingress.yaml file modifies the path definition for the MinIO service, removing a trailing slash and adding a new path for the GraphQL endpoint.

Changes

File Path Change Summary
charts/plane-ce/templates/config-secrets/app-env.yaml Enhanced Secret and ConfigMap with new data entries: SENTRY_DSN, SENTRY_ENVIRONMENT, DEBUG, DOCKERIZED, GUNICORN_WORKERS, WEB_URL, CORS_ALLOWED_ORIGINS, REDIS_URL, DATABASE_URL, AMQP_URL.
charts/plane-enterprise/Chart.yaml Version updated from 1.0.12 to 1.1.0.
charts/plane-enterprise/templates/ingress.yaml Modified path for MinIO service from /{{ .Values.env.docstore_bucket }}/ to /{{ .Values.env.docstore_bucket }}. Added new path for GraphQL endpoint.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Ingress
    participant MinIO
    participant API

    User->>Ingress: Request to MinIO
    Ingress->>MinIO: Route request to /{{ .Values.env.docstore_bucket }}
    MinIO-->>Ingress: Response
    User->>Ingress: Request to GraphQL
    Ingress->>API: Route request to /graphql/
    API-->>Ingress: Response
    Ingress-->>User: Return responses
Loading

🐇 "In the land of code, changes abound,
Secrets and configs, new values found.
With paths redefined, we hop with glee,
Version updates and flexibility!
Let's celebrate with a joyful cheer,
For every change brings us near!" 🐇

Possibly related PRs


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4a54100 and a523dca.

📒 Files selected for processing (1)
  • charts/plane-enterprise/Chart.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • charts/plane-enterprise/Chart.yaml

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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: 1

🧹 Outside diff range and nitpick comments (1)
charts/plane-ce/templates/config-secrets/app-env.yaml (1)

9-9: Remove trailing whitespace.

There is trailing whitespace on this line that should be removed.

-  
+
🧰 Tools
🪛 yamllint

[error] 9-9: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c513a82 and 3936bd6.

📒 Files selected for processing (1)
  • charts/plane-ce/templates/config-secrets/app-env.yaml (1 hunks)
🧰 Additional context used
🪛 yamllint
charts/plane-ce/templates/config-secrets/app-env.yaml

[error] 9-9: trailing spaces

(trailing-spaces)

🔇 Additional comments (2)
charts/plane-ce/templates/config-secrets/app-env.yaml (2)

Line range hint 39-59: Verify connection URL patterns.

The database and message queue connection strings should be validated to ensure they follow the expected format. Consider adding validation helpers or documentation for the expected URL patterns.

Let's check for any existing URL validation or documentation:

#!/bin/bash
# Search for URL validation or connection string documentation
rg -i "(database|redis|amqp).?url.?(format|pattern|validation)" --type md
🧰 Tools
🪛 yamllint

[error] 9-9: trailing spaces

(trailing-spaces)


[error] 6-6: syntax error: expected , but found ''

(syntax)


Line range hint 27-37: Enhance CORS configuration validation.

The CORS configuration could benefit from additional validation to ensure secure defaults:

  1. When cors_allowed_origins is "*", it allows all origins which might be too permissive
  2. There's no validation for malformed URLs in the custom CORS origins

Let's check if there are any security guidelines or documentation about CORS configuration:

#!/bin/bash
# Search for CORS-related documentation or security guidelines
rg -i "cors.?(allowed.?origins|security|configuration)" --type md
🧰 Tools
🪛 yamllint

[error] 9-9: trailing spaces

(trailing-spaces)


[error] 6-6: syntax error: expected , but found ''

(syntax)

@sriramveeraghanta sriramveeraghanta merged commit 2c851fb into develop Nov 25, 2024
1 check passed
@sriramveeraghanta sriramveeraghanta deleted the fix-uploads branch November 25, 2024 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants