Dynamically define Kibana image tag to use

[BMartinos]

To allow this to be configurable based on project needs

Summary by CodeRabbit

• New Features

  • Introduced the ability to dynamically set the Kibana image version using the KIBANA_IMAGE_TAG environment variable.

• Configuration

  • Updated the Kibana image configuration to use a variable for the version, enhancing flexibility and ease of updates.

[coderabbitai]

Walkthrough

The updates in the project involve making the Kibana image tag configurable via an environment variable ${KIBANA_IMAGE_TAG} in the docker-compose.yml file. This change enhances flexibility and maintainability by allowing the image version to be set dynamically. Additionally, the package-metadata.json file is updated to include this new environment variable with a default value of "7.13.0".

Changes

Files	Change Summary
dashboard-visualiser-kibana/docker-compose.yml	Updated Kibana image tag to use a variable ${KIBANA_IMAGE_TAG} instead of a hardcoded version.
dashboard-visualiser-kibana/package-metadata.json	Added environment variable KIBANA_IMAGE_TAG with the value "7.13.0".

🐇
In the land of code, where changes bloom,
A variable now sets the Kibana tune.
Flexibility we gain, with tags that change,
Our docker-compose now feels less strange.
🌼✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[coderabbitai]

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 67e1a49 and 9bde5d5.

Files selected for processing (2)

• dashboard-visualiser-kibana/docker-compose.yml (1 hunks)
• dashboard-visualiser-kibana/package-metadata.json (1 hunks)

Files skipped from review due to trivial changes (2)

• dashboard-visualiser-kibana/docker-compose.yml
• dashboard-visualiser-kibana/package-metadata.json

[BMartinos]

Closing this PR as these changes have already been addressed in #287