Support scopes flag in gp env

[loujaybee]

Currently gp env allows you to set an environment variable, but it automatically sets the scope (of the environment variable) as the current repo, we should extend the command to allow any wildcard to be input.

Steps to replicate:

• Go to a workspace
• Run gp env SCOPE_TEST=temp
• View the environment variable in the dashboard

e.g.

The default behaviour makes sense, but we should consider extending with a flag such as --scope=repo which will allow the user to specify the scopes of the environment variable.

Related: #6308 (comment)

[iQQBot]

/assign

[iQQBot]

@loujaybee i think it need discussion
For set env --scope=repo is better understood
How do we define the Get and Delete behaviors?

current unset

Note that you can delete/unset variables if their repository pattern matches the repository of this workspace exactly. I.e. you cannot delete environment variables with a repository pattern of */foo, foo/* or */*.

current get can get environment variables with a repository pattern of */foo, foo/* or */*.

Should we keep it the same? Or do we also need to add the --repo parameter?

[iQQBot]

@loujaybee have any ideas?

[iQQBot]

/unassign

[chuck-alt-delete]

@iQQBot maybe on first iteration just add the ability to set scope for set and leave the rest unchanged?

nevermind — see next comment. I thought about it some more

[chuck-alt-delete]

Maybe keep this in mind too:

• regex support for environment variable scope #7822

We might someday want to pass a regex for the —scope parameter.

So maybe

• set: create the env variable scoped to the given scope
• Get: get all environment variables for which the current repo matches the scope (which is possibly regex)
• Delete: delete env variable if the scope of that variable matches the —scope given, otherwise tell user that it was not deleted. This forces the user to understand the impact of deleting the variable.

[m-Bilal]

@loujaybee , @chuck-alt-delete Hi! I'm new to the Gitpod community. Can I please take this up?

[loujaybee]

@m-Bilal sure thing 👍

[stale]

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.

[axonasif]

Not stale 😄

[stale]

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]

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.