Add ability to export current values of the environment

[IsrraBanton]

Describe the bug The postman's enviroments have Initial and current value but when I save I got the initial value in the json file

To Reproduce Steps to reproduce the behavior:

1. Go to any enviroment
2. Create a new variable
3. Set differentes value in initial value and current value of your variable
4. Export enviroment and save the json file
5. Delete the enviroment and import from json file.
6. Check initial and current value of your variable. Will be the same value.

Expected behavior When I save an enviroment I speck to get in my Json current and initial value, but if It's not possible I need at least to save the current value.

[codenirvana]

@IsrraBanton That's by design and you can know more about variable sessions here: https://blog.getpostman.com/2018/08/09/sessions-faq/

Changing this to feature request and updating the issue title accordingly.

[Boorda]

@IsrraBanton That's by design and you can know more about variable sessions here: https://blog.getpostman.com/2018/08/09/sessions-faq/

Changing this to feature request and updating the issue title accordingly.

This would be good as an export Option, defaulted to false.

Also, it may make it more apparent that session variables are not exported (or by default if option is implemented) if the info icons next to the INITIAL VALUE & CURRENT VALUE included a statement about exporting.

[dzar-aker]

I have been hit by this issue, as well.

A scenario that I think should be considered:

• User with many environments for testing has locally defined passwords and other sensitive information
• This user gets a new computer
• User needs to get their complete Postman setup running on new machine as quickly as possible.

Currently, this is quite difficult and manual.

1. There is no way to export the local changes to an environment
2. There is no way to export ALL environments with one click/command

These should both be resolved. Just like I can export a collection, I should be able to export "environments" to one file with the option of exporting the local changes. That would solve this need, I think.

Right now, this is a very painful process and results in a loss of productivity as it's mostly manual and needs a lot of verification to be sure each environment has moved over properly.

[ggo98]

Would like the same feature too... (an option to export the current values of an environment)

[serbrio]

+1

[caetanope]

+1

[dtoomey]

++1. Please add this feature!!

[Mgajurel]

+1. Please, this has been a pain.

[tasosz]

but if It's not possible I need at least to save the current value.

It doesn't look possible to have both on export still. But, by using the "Persist All" option (top right of the env pane), the current values are auto-copied to the initial values. Then the export has the values you need.

[Mgajurel]

but if It's not possible I need at least to save the current value.

It doesn't look possible to have both on export still. But, by using the "Persist All" option (top right of the env pane), the current values are auto-copied to the initial values. Then the export has the values you need.

@tasosz Thanks for the work around.

[maur1ce-m]

but if It's not possible I need at least to save the current value.

It doesn't look possible to have both on export still. But, by using the "Persist All" option (top right of the env pane), the current values are auto-copied to the initial values. Then the export has the values you need.

I will still have to remove sensitive data from Initial Values after importing.

@tasosz Thanks for the work-around 🙌

[shishir20may2022]

+1

[gbhosal]

+1

[hero3616]

+1

[Neutrino-Sunset]

This entire Initial Value/ Current Value design is just plain daft.

1. I only care what the value of any variable actually is (current value), why would I ever care what the value of any variable isn't (initial value)?
2. If I'm exporting an environment, why would I ever want to export the variables with values that are different to what they actually are? That's not even exporting!
3. Since you can edit all the initial values to whatever you want (which you have to do manually before you export the environment) then in what sense are they even the initial values anyway?

Bizarre.

[abhijeetborole]

@Neutrino-Sunset Current values are intended to be used locally for sensitive data.

As for having to manually update all initial values before exporting by persisting.

https://github.com/user-attachments/assets/69b68975-a87b-42f1-9d2a-2c41f6335399

[Neutrino-Sunset]

So there is a quicker way to do an export that works, fair enough.

I still say it's highly unintuitive though. I think the names Initial Value and Current Value are part of the problem. They are just not correct since if you export you don't get the current value at all.

I think they should be called 'Persisted Value' and 'Active Value'

[jola16]

1. I agree on the renaming suggestion from @Neutrino-Sunset .

2. @abhijeetborole : I do not want to persist my local values as our environments normally are shared with a lot of people who must not have access to my local values.

The easiest and most straightforward solution would be to simply allow the user to select that they want to include the 'Active/Current Values' in the export. The filename of the export could/should then default to a name that makes it clear to the user that the file contains "Active/Current" values.

This request was opened in 2019 so I don't see the point anymore in discussing why we need this functionality. The real question is how prioritized this should be be compared to the 1930 other feature requests (plus bugs) that are in the backlog for Postman...?