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

Allow multiple scopes in env variables #12877

Open
thisisommore opened this issue Sep 12, 2022 · 6 comments
Open

Allow multiple scopes in env variables #12877

thisisommore opened this issue Sep 12, 2022 · 6 comments
Labels

Comments

@thisisommore
Copy link

thisisommore commented Sep 12, 2022

Is your feature request related to a problem? Please describe

Creating and managing enviroment variables with only one scope is hard, for example, I want to create env SECRET for repos under my user thisisommore and under my company lazarus which is only possible with *\* since lazarus/*,thisisommore/* is not possible and I will get this error if I try to do so
image

Describe the behaviour you'd like

I would like to use comma or some separator or some UI to create multiple scopes

Describe alternatives you've considered

Create two variables entries for each scope

Additional context

@loujaybee
Copy link
Member

Thanks @thisisommore for the feedback! Housekeeping: This looks like it was originally assigned to IDE team, I think this is more related to WebApp, however? I also couldn't find a label for the environment variables feature, we could possibly do with one. Assigned to WebApp team inbox.

@geropl
Copy link
Member

geropl commented Sep 15, 2022

@thisisommore Wouldn't using two variables solve the issue here? 🤔

@axonasif
Copy link
Member

Having parameter expansion just feels more nice for the peace of mind 😝

Screenshot 2022-09-15 at 8 52 21 PM

@thisisommore
Copy link
Author

thisisommore commented Sep 15, 2022

@thisisommore Wouldn't using two variables solve the issue here? 🤔

Not the good UX, It clutters the UI due to duplication. One env variable with exact same value but double entries due to different scopes doesn't make sense

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

5 participants