Closed djjudas21 closed 4 months ago
[!WARNING]
Rate limit exceeded
@djjudas21 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 55 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between f19f44414a370b36e947482905cae508410d89d5 and 78e28cfc014a570d39b656f2f6ac6dd6a0b3e337.
The primary change introduced is the enhancement and expansion of the charts/authelia
Helm chart to include optional Bitnami subcharts for Redis, PostgreSQL, and MariaDB. This allows for an integrated deployment of these services using new configuration flags. Additionally, the .helmignore
file has been modified to no longer exclude *.tgz
files.
Files/Directories | Change Summary |
---|---|
charts/authelia/.helmignore | Removed the exclusion pattern for *.tgz . |
charts/authelia/README.md | Updated to include details on deploying optional Redis, PostgreSQL, and MariaDB using Bitnami subcharts. New flags for deployment control were introduced. |
sequenceDiagram
participant User as User
participant HelmChart as Authelia Helm Chart
participant Redis as Redis Subchart
participant PostgreSQL as PostgreSQL Subchart
participant MariaDB as MariaDB Subchart
User->>HelmChart: Deploy Authelia with optional dependencies
alt Redis Enabled
HelmChart->>Redis: Deploy Redis
end
alt PostgreSQL Enabled
HelmChart->>PostgreSQL: Deploy PostgreSQL
end
alt MariaDB Enabled
HelmChart->>MariaDB: Deploy MariaDB
end
Note right of MariaDB: Optional subcharts deployed based on user configuration
Objective | Addressed | Explanation |
---|---|---|
Enable optional dependencies for Redis and PostgreSQL using helm optional dependencies (#172, #89) | ✅ | |
Ensure backward compatibility by defaulting the new options to off (#172) | ✅ | |
Include detailed documentation for the new configuration options in the README.md (#172, #89) | ✅ |
[!TIP]
Early access features: enabled
We are currently testing the following features in early access: - **OpenAI `gpt-4o` model for code reviews and chat**: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available. Note: - You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file. - Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide feedback and report issues. - OSS projects are always opted into early access features.
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?
This PR adds basic support for deploying Redis, MariaDB or PostgreSQL as part of an Authelia deployment.
Typically the dependency subcharts would be integrated under the top level
mariadb:
orpostgresql:
keys, where the config can be inherited by the subcharts, and the main app (i.e. Authelia) would also draw its config from those keys. However the database config in the chart is understorage.mysql
andstorage.postgres
and changing this would be a breaking change.So I have added booleans
storage.redis.deploy
,storage.mysql.deploy
andstorage.postgres.deploy
which enable the user to deploy the Bitnami subcharts. This does not affect any existing Authelia deployments. At the moment the user has to copy a few settings (e.g. credentials) from themariadb
section to thestorage.mysql
section.In future we could consider a tighter integration, but it would be a more major refactoring, so let's go with this for now.
I have tested this chart on my own deployment with MariaDB and PostgreSQL databases, plus Redis.