Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New base environment created on each import #5558

Open
1 task done
rbideau opened this issue Dec 20, 2022 · 1 comment
Open
1 task done

New base environment created on each import #5558

rbideau opened this issue Dec 20, 2022 · 1 comment
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer

Comments

@rbideau
Copy link

rbideau commented Dec 20, 2022

Expected Behavior

Base environment id is stable, no new base environment is created when one already exists on import.

Actual Behavior

Base environment id is always re-generated when importing, resulting in loss of sub-environments.

Reproduction Steps

  1. Install plugin Repo Sync Plugin v3
  2. Configure plugin
  3. Create a new collection
  4. Create a request, an environment
  5. Export workspace
  6. Import workspace
  7. Re-Export workspace
InsomniaSyncEnvironment.webm

Is there an existing issue for this?

Additional Information

When importing a collection, a new base environment is created on each import.

This break the plugin Repo Sync Plugin v3 which use the import/export api to synchronize collection.

This is likely introduced by #4378

Insomnia Version

2022.7.0

What operating system are you using?

Ubuntu

Operating System Version

20.04.1

Installation method

apt

Last Known Working Insomnia version

2022.6.0

@rbideau rbideau added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Dec 20, 2022
@rbideau rbideau changed the title New base environemnt created on each import New base environment created on each import Dec 20, 2022
@gatzjames gatzjames mentioned this issue Mar 31, 2023
10 tasks
@NickRimmer
Copy link

Probably connected to this issue #5942

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer
Projects
None yet
Development

No branches or pull requests

2 participants