Skip to content

EPMRPP-113780 || Update 'S3 Cloud Storage' article#1095

Merged
maria-hambardzumian merged 1 commit intodevelopfrom
EPMRPP-113780
Mar 24, 2026
Merged

EPMRPP-113780 || Update 'S3 Cloud Storage' article#1095
maria-hambardzumian merged 1 commit intodevelopfrom
EPMRPP-113780

Conversation

@pressayuliya
Copy link
Copy Markdown
Contributor

@pressayuliya pressayuliya commented Mar 23, 2026

Summary by CodeRabbit

  • Documentation
    • Updated S3/JClouds cloud storage configuration documentation with clearer environment variable scoping across services and APIs for improved configuration clarity
    • Added new environment variables reference section for Analyzer with S3-specific configuration settings including bucket configuration options
    • Enhanced docker-compose deployment examples with revised datastore type specification and service-specific feature flag configurations

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 23, 2026

Walkthrough

Updated S3 cloud storage documentation to use DATASTORE_TYPE: s3 instead of aws-s3, clarified service applicability for environment variables, and added new Analyzer-specific configuration sections with dedicated environment variable anchors for docker-compose examples.

Changes

Cohort / File(s) Summary
S3 CloudStorage Documentation
docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md
Updated datastore type from aws-s3 to s3, added clarification on which services use listed environment variables, introduced new "Environment variables for Analyzer" section with x-analyzer-environment YAML anchor, and extended IAM role-based docker-compose example with feature flags (singleBucket) and separate analyzer-specific S3 configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Hopping through the docs with glee,
S3 storage, now set to be,
From aws-s3 to the modern way,
Analyzer configs shine today!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the documentation update to the S3 Cloud Storage article, which aligns with the changes in the raw summary.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch EPMRPP-113780

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@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: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md`:
- Line 26: Fix the typo in the markdown header by removing the duplicated word:
replace the header string "**Environment variables for for Analyzer:**" with
"**Environment variables for Analyzer:**" (look for that exact header text in
S3CloudStorage.md and update it).
- Around line 28-36: Update the Analyzer environment block to clarify region
format and correct the bucket name: add a comment beside DATASTORE_REGION
explaining it uses the AWS region format (e.g., us-east-1) as opposed to
JClouds’ names, and change DATASTORE_DEFAULTBUCKETNAME from
"my-rp-docker-bucket/analyzer" to a valid bucket name "my-rp-docker-bucket"
(move the "/analyzer" path into the object key prefix mechanism such as
DATASTORE_BUCKETPREFIX or document using DATASTORE_BUCKETPREFIX for object path
prefixes) so the S3 bucket name conforms to AWS naming rules.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e15a8044-a0c3-4c8c-97ed-6eb349b67db8

📥 Commits

Reviewing files that changed from the base of the PR and between b5df2a1 and 3f51918.

📒 Files selected for processing (1)
  • docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md

DATASTORE_DEFAULTBUCKETNAME: my-bucket # Name of the bucket
```

**Environment variables for for Analyzer:**
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix the duplicate word in the header.

The header contains a typo: "for for Analyzer" should be "for Analyzer".

📝 Proposed fix
-**Environment variables for for Analyzer:**
+**Environment variables for Analyzer:**
📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Environment variables for for Analyzer:**
**Environment variables for Analyzer:**
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md` at
line 26, Fix the typo in the markdown header by removing the duplicated word:
replace the header string "**Environment variables for for Analyzer:**" with
"**Environment variables for Analyzer:**" (look for that exact header text in
S3CloudStorage.md and update it).

Comment on lines +28 to +36
```bash
x-analyzer-environment: &common-analyzer-environment
DATASTORE_REGION: us-east-1
DATASTORE_ACCESSKEY: "<access_key>"
DATASTORE_SECRETKEY: "<secret_key>"
DATASTORE_BUCKETPREFIX: prj-
DATASTORE_BUCKETPOSTFIX: ""
DATASTORE_DEFAULTBUCKETNAME: my-rp-docker-bucket/analyzer
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify DATASTORE_REGION and bucket name configuration patterns

# Search for DATASTORE_REGION usage patterns
rg -n -C2 'DATASTORE_REGION.*us-(east-1|standard)' --type=md --type=yaml

# Search for bucket name patterns with slashes
rg -n 'DATASTORE.*BUCKET.*/' --type=md --type=yaml

# Search for documentation about bucket prefix/postfix usage
rg -n -C3 'BUCKETPREFIX|BUCKETPOSTFIX' --type=md

Repository: reportportal/docs

Length of output: 4584


🏁 Script executed:

# Get broader context around the snippet to understand the configuration sections
sed -n '17,50p' docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md

Repository: reportportal/docs

Length of output: 1238


🏁 Script executed:

# Get the full file to understand documentation structure and clarifications
wc -l docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md

Repository: reportportal/docs

Length of output: 136


🏁 Script executed:

# Search for explanations about bucket naming conventions in the file
rg -n -C5 'bucket.*name|bucket.*notation|slash|path' docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md -i

Repository: reportportal/docs

Length of output: 4256


🏁 Script executed:

# Search for any warnings or notes about S3 bucket name format restrictions
rg -n -C3 'S3.*name|bucket.*format|slash|cannot|invalid' docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md -i

Repository: reportportal/docs

Length of output: 740


Fix bucket name format and add clarifying comment for region format in Analyzer section.

Two issues require attention:

  1. Missing region format clarification: Line 30 uses us-east-1 without a comment explaining why it differs from the JClouds format (us-standard) used in line 20. Add a clarifying comment like the one on line 20 or line 360.

  2. Invalid bucket name with slash: Line 35 (and line 374) contains my-rp-docker-bucket/analyzer for DATASTORE_DEFAULTBUCKETNAME. S3 bucket names cannot contain forward slashes per AWS bucket naming rules. The bucket name should be my-rp-docker-bucket, and the /analyzer path should be handled as an object key prefix using DATASTORE_BUCKETPREFIX or similar mechanism (compare to line 361 which correctly shows only my-rp-docker-bucket for the bucket name).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/installation-steps-advanced/file-storage-options/S3CloudStorage.md`
around lines 28 - 36, Update the Analyzer environment block to clarify region
format and correct the bucket name: add a comment beside DATASTORE_REGION
explaining it uses the AWS region format (e.g., us-east-1) as opposed to
JClouds’ names, and change DATASTORE_DEFAULTBUCKETNAME from
"my-rp-docker-bucket/analyzer" to a valid bucket name "my-rp-docker-bucket"
(move the "/analyzer" path into the object key prefix mechanism such as
DATASTORE_BUCKETPREFIX or document using DATASTORE_BUCKETPREFIX for object path
prefixes) so the S3 bucket name conforms to AWS naming rules.

@maria-hambardzumian maria-hambardzumian merged commit 464d767 into develop Mar 24, 2026
2 checks passed
@maria-hambardzumian maria-hambardzumian deleted the EPMRPP-113780 branch March 24, 2026 08:51
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.

2 participants