-
Notifications
You must be signed in to change notification settings - Fork 669
Wrong behaviour deleting variable #1387
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
Comments
I run into the same issue at the same time! :)
Works for me. |
I've confirmed that this workaround does work. However this can delete unwanted variables if we don't make sure that the environment scope in the filter is not the same as the one on the variable we fetched. |
sadly, there is no other method in the underlying v4 api. |
But it is possible to alter the |
It seems like the manager could default to specifying that filter if the |
Description of the problem, including code/CLI snippet
On a project where we have the same variable names in different environments, running the code below to delete a variable produces a scope error when running it.
Expected Behavior
Successful variable deletion
Actual Behavior
Produces the error below:
Specifications
The text was updated successfully, but these errors were encountered: