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

Introduce gp command to add env from .env file #12243

Closed
thisisommore opened this issue Aug 20, 2022 · 8 comments
Closed

Introduce gp command to add env from .env file #12243

thisisommore opened this issue Aug 20, 2022 · 8 comments
Labels
component: gp cli feature: environment variables meta: stale This issue/PR is stale and will be closed soon team: IDE type: feature request New feature or request

Comments

@thisisommore
Copy link

Is your feature request related to a problem? Please describe

When we have .env file with variables already there and we want to persist that in gitpod way using gp env we have to manually run the command gp env KEY=value for each variable, which decreases my productivity for setting new repos

Describe the behaviour you'd like

I would like to run command which reads and specified file like .env and persist that key and values of environment variables for that repo, like what gp env does.
For example

$ gp env-read .env
> 13 Environments added

Describe alternatives you've considered

Additional context

@axonasif
Copy link
Member

Hey @thisisommore 👋

As a workaround for now you can use the following to save your time:

while read -r line; do {
   [[ ! "$line" =~ ^\# ]] && gp env "$line";
} done < .env

@stale
Copy link

stale bot commented Dec 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Dec 16, 2022
@thisisommore
Copy link
Author

@axonasif can this be never stale?

@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Dec 17, 2022
@axonasif
Copy link
Member

axonasif commented Dec 23, 2022

@thisisommore let's comment each time when stalebot tries to close this issue 🙂

@thisisommore
Copy link
Author

@axonasif can we add meta: never-stale instead 😃

@axonasif
Copy link
Member

I added it to one of your other issue that was also stale.

@thisisommore
Copy link
Author

@axonasif I don't get it
So this issue will also act as never stale?
Are this two(this and one #12877) issues linked anywhere?

@stale
Copy link

stale bot commented Apr 2, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Apr 2, 2023
@stale stale bot closed this as completed Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: gp cli feature: environment variables meta: stale This issue/PR is stale and will be closed soon team: IDE type: feature request New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants