13
Environment Import/Export or Selective Project Export
Source: Kong/insomnia#6203 · opened by @andreassiegel
In Insomnia, it is possible to selectively export collections but environments cannot be imported and exported the same way. The only way is to export/import the entire Insomnia project which might be too much.
It would be nice to be able to handle export and import environments just like collections.
Alternatively, it would be great if it was possible to select what to include in a project export.
For instance, we have the strict requirement to work "offline", i.e., withouth any data being synced to the cloud, therefore, we are working with different collections in the "Insomia" default project/organization. These collections relate to different actual products of the same and we don't always want to export everything together.
It would be nice to be able to handle export and import environments just like collections.
Alternatively, it would be great if it was possible to select what to include in a project export.
For instance, we have the strict requirement to work "offline", i.e., withouth any data being synced to the cloud, therefore, we are working with different collections in the "Insomia" default project/organization. These collections relate to different actual products of the same and we don't always want to export everything together.
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow canceling "Import from File" -> "Existing" operation
2 votes · 0 comments
Redesign the environment variables
1 vote · 0 comments
Ability to toggle multiple environments
17 votes · 0 comments
Allow plugins synchronize to workspace
1 vote · 0 comments
Import option to not create new environment
1 vote · 0 comments
No comments yet.