Development: Configure telemetry variables for e2e tests

[pzdr7]

Checklist

General

• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Since #9174, we need to specify the info.operatorName before starting Artemis. The Playwright E2E tests on Bamboo do not do this yet, so they crash immediately.

Description

Modified the playwright environment:

• Disabled Telemetry
• Set an operator name

Steps for Testing

Check that the Playwright E2E tests on Bamboo don't fail as a "testless build." (failing E2E tests are okay, so long as they actually run)

(Example of a failing build on develop: https://bamboo.ase.in.tum.de/browse/ARTEMIS-AEPTMA-479)

Review Progress

Code Review

• Code Review 1
• Code Review 2

Summary by CodeRabbit

• New Features
  • Introduced new configuration options for enhanced user control over telemetry and operational information.
    • Telemetry features are now disabled by default, allowing users to prioritize privacy.
    • Added operator name configuration for improved logging and monitoring clarity.

[coderabbitai]

Walkthrough

The changes introduce two new configuration variables to the playwright.env file: ARTEMIS_TELEMETRY_ENABLED, which controls the telemetry feature and is set to "false" by default, and INFO_OPERATORNAME, which specifies the operator's name as "TUM". These additions enhance configuration options for system administrators.

Changes

File	Change Summary
docker/artemis/config/playwright.env	Added ARTEMIS_TELEMETRY_ENABLED="false" and INFO_OPERATORNAME="TUM" declarations.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between e64be2d and 945ea8f.

Files selected for processing (1)

• docker/artemis/config/playwright.env (2 hunks)

Additional comments not posted (2)

docker/artemis/config/playwright.env (2)

30-30: Configuration for telemetry is correctly disabled.

The addition of ARTEMIS_TELEMETRY_ENABLED="false" is a crucial update for controlling telemetry features, especially in testing environments where privacy or resource management might be a concern. This change aligns with the PR objectives to ensure that the E2E tests can run without the telemetry configuration causing issues.

---

43-43: Operator name configuration is set appropriately.

The setting of INFO_OPERATORNAME="TUM" is a straightforward and necessary addition for specifying the operator's name, which is required by the Artemis application to run properly. This configuration helps in maintaining operational clarity and is essential for the correct functioning of the E2E tests as mentioned in the PR objectives.

---

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.
  • @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 or @coderabbitai title 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.