Skip to content

Fix/multi environment import fails entirely if one file is invalid - #9051

Draft
Gopi-bruno wants to merge 12 commits into
usebruno:mainfrom
Gopi-bruno:fix/multi-environment-import-fails-entirely-if-one-file-is-invalid
Draft

Fix/multi environment import fails entirely if one file is invalid#9051
Gopi-bruno wants to merge 12 commits into
usebruno:mainfrom
Gopi-bruno:fix/multi-environment-import-fails-entirely-if-one-file-is-invalid

Conversation

@Gopi-bruno

@Gopi-bruno Gopi-bruno commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

BRU-3674

Description

This PR is built above the PR-9050 which introduces a modal when the user imports duplicate environments (with name conflicts) and provides the user with an option to import as copy/replace those envs. But if one of the env is malformed/invalid/corruped, we fail the import totally which is causing the user to reimport with specifically cherry-picking the valid env files again. This PR introduces a separate accordion to inform the user about the corrupted files and let the user import envs from the rest of the files whichout breaking the whole import process.

Problem

Failure to import the valid envs, if only one/few of them is invalid.

Fix

We'll inform the user about the invalid env files and still give the user an option to import envs from valid files.

Screenshots

Before

Screen.Recording.2026-08-24.at.6.06.38.PM.mov

After

Screen.Recording.2026-08-24.at.6.07.36.PM.mov

Contribution Checklist:

  • I've used AI significantly to create this pull request
  • The pull request only addresses one issue or adds one feature.
  • The pull request does not introduce any breaking changes
  • I have added screenshots or gifs to help explain the change if applicable.
  • I have read the contribution guidelines.
  • Create an issue and link to the pull request.
  • I've run the claude code review skill locally.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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.

…s and apply theme-aware accent colors in ImportEnvironmentModal
… environment imports without naming conflicts
…importing-environments' into fix/multi-environment-import-fails-entirely-if-one-file-is-invalid
…flicts exist and improve error handling for malformed files
…on and update accessibility attributes for selection buttons
…importing-environments' into fix/multi-environment-import-fails-entirely-if-one-file-is-invalid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant