Skip to content

fix: Ingestion of buckets not working right after connection is tested - CPD #75506#1942

Open
ricofurtado wants to merge 3 commits into
release-cpd-0.1from
fix-cpd-ingestion-of-buckets-not-working-right-after-connection-is-tested-75506
Open

fix: Ingestion of buckets not working right after connection is tested - CPD #75506#1942
ricofurtado wants to merge 3 commits into
release-cpd-0.1from
fix-cpd-ingestion-of-buckets-not-working-right-after-connection-is-tested-75506

Conversation

@ricofurtado

@ricofurtado ricofurtado commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

This pull request updates the S3 and IBM Cloud Object Storage (IBMCOS) settings and upload flows to improve clarity for users and to support initializing the bucket selection with default values. The main changes include updating user-facing labels and messages for better clarity, and adding logic to pre-select default buckets when presenting the bucket selection UI.

User interface and messaging improvements:

  • Updated labels and descriptions in both S3 and IBMCOS settings forms to use clearer wording: "Restrict to Specific Buckets" and "(leave all unchecked to include all)" instead of the previous "Select Buckets to Ingest" messaging. [1] [2]
  • Changed success toast messages in both S3 and IBMCOS settings dialogs to use "Filtered to: ..." and "All accessible buckets are included." for improved clarity. [1] [2]

Bucket selection initialization enhancements:

Summary by CodeRabbit

  • New Features

    • Added support for pre-selecting buckets when uploading to Amazon S3 and IBM Cloud Object Storage based on connector configuration.
  • Improvements

    • Updated bucket selector UI labels and confirmation messages for improved clarity about bucket filtering and inclusion options.

@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: efdd4fd4-f60d-41a8-be03-8186de7a48fd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The PR title focuses on fixing bucket ingestion workflow after connection testing, but the actual changes are primarily UI text updates to bucket selector labels and success messages, plus a feature to support pre-selecting buckets via connector defaults. Clarify whether the title accurately reflects the primary changes (UI text updates and bucket pre-selection feature) or if the actual fixes to ingestion logic should be more prominently featured in the changeset.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ 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 fix-cpd-ingestion-of-buckets-not-working-right-after-connection-is-tested-75506

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.

@github-actions github-actions Bot added the frontend 🟨 Issues related to the UI/UX label Jun 22, 2026
@ricofurtado ricofurtado changed the title CPD - Ingestion of buckets not working right after connection is tested #75506 CPD - Ingestion of buckets not working right after connection is tested 75506 Jun 22, 2026
@ricofurtado ricofurtado changed the title CPD - Ingestion of buckets not working right after connection is tested 75506 fix:Ingestion of buckets not working right after connection is tested - CPD #75506 Jun 22, 2026
@github-actions github-actions Bot added the bug 🔴 Something isn't working. label Jun 22, 2026
@ricofurtado ricofurtado changed the title fix:Ingestion of buckets not working right after connection is tested - CPD #75506 fix: Ingestion of buckets not working right after connection is tested - CPD #75506 Jun 22, 2026
@github-actions github-actions Bot added bug 🔴 Something isn't working. and removed bug 🔴 Something isn't working. labels Jun 22, 2026
The defaults query returns the first S3/COS connection regardless of active
status. Only pre-select saved bucket_names when the defaults connection_id
matches the current connector.connectionId to avoid seeding the wrong
buckets if a stale connection exists alongside the active one.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot added bug 🔴 Something isn't working. and removed bug 🔴 Something isn't working. labels Jun 22, 2026
Two issues in the initial-selection effect:
1. hasAppliedInitial was only set when valid buckets were found, leaving the
   effect live across bucket refreshes and allowing stale defaults to overwrite
   selections made after a refetch.
2. No guard against the async race where buckets loads before initialSelectedBuckets:
   user clicks buckets, defaults arrive later and silently overwrite them.

Fix: mark hasAppliedInitial unconditionally on first evaluation, and only apply
defaults when selectedBuckets is still empty (user hasn't acted yet).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot added bug 🔴 Something isn't working. and removed bug 🔴 Something isn't working. labels Jun 23, 2026
@github-actions github-actions Bot added the lgtm label Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug 🔴 Something isn't working. frontend 🟨 Issues related to the UI/UX lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants