Add an export primitive to use with eval to simplify exporting variables

[loopingz]

Issue #, if available:
#6962

As some of the tools i use need the environment variable to be set, switching from one profile to another was painfull, by adding this method i can just run

eval aws configure export --profile myprofile

Going back to the default with

eval aws configure export

I would have prefered to export the variables from Python directly but it looks like it is not possible

[loopingz]

Any chances to have some feedback on this feature ?

[dstufft]

Personally I'm a little uncomfortable with this feature, largely because the question of how to export environment variables is going to be very shell dependent, for example this is going to fail with the fish shell.

Perhaps the others might have a different opinion though.

[loopingz]

Agreed that it is largely shell depend, i'm open to any changes to make it less shell dependent, I'm just looking into fish to see if i can find something. I'm using my modified version of aws cli on daily basis and it was really usefull for me to switch from one aws account to another

[loopingz]

Do you have any updates on this ?

Regards

[loopingz]

I did create a yaws project on pip to allow my users to use the export, is there any chance to have this PR merge ?

[loopingz]

@stealthycoin or @dstufft should I remove the pull request or is there any chances it makes it to the project? Thank you

[justindho]

Hi @loopingz,

Our team just put out a recent proposal in #6828 detailing improvements to the contribution process. We are working through open PRs and are trying to determine where this feature request falls.

For feature requests, to invest the time in reviewing it, we would like to make sure the feature has wider community interest and are looking for 10 👍 votes on the linked issue. For the currently open PR, we are going to set it as a draft. Once the 👍 threshold is met, we will move it to the “Contribution Ready” state.

[loopingz]

@justindho this PR for example got so many +1 for no result: #2710 and was just closed as is.

For this issue, I created this repository https://github.com/loopingz/yaws/stargazers
It has some stars from the community, pip does not keep track of number of downloads.

Also, I'd like to mention that we are talking about PR that were created in 2017... I'm glad to have someone finally working on it.

[tim-finnigan]

Checking in - thanks for your patience and for creating this PR. I think this had fallen off of the team's radar but it looks like the feature has now been implemented via #7398.

I hope that addresses your use case. For feature requests related to this command you can create a new issue for further review. Please let us know if you had any follow up questions or feedback.