Four years later this has still not been implemented by Octopus?

I found some stuff here though: https://github.com/OctopusDeploy/OctopusDeploy-Api/tree/master/REST/PowerShell/Variables

Also need the ability to search variables for a value. I think this could have been handled by having some basic server variable where we define the IP or DNS Name and then use that server variable in other variables.

Also helpful would be the ability to filter variables for just a given scope.

Another option would be the ability to do a search and replace.

I could sure use the ability to search for variables that contain a specific value. I needed it today and there have been several times over the past few years I have needed that ability. Alternatively, being able to "search all Octopus objects (variables, steps, templates, scripts, etc.) for a value so to identify where updates may be needed" would be even more useful.

If it was possible to define the scope of the search (all of Octopus, just steps, variables, pre/post-steps). But the same need stands to reason. migrating from old to new servers and changing all variables/settings in steps is very timeconsuming and errorprone without any way to find those values to change. When you go beyond 60 Projects it becomes a daunting task

I would also love to be able to search for a variable value. We're decommissioning a server and moving a bunch of services to the new instance and while most of our services refernce a dns name that will not change, there ois still a chance that w have some variables that reference the ip, and currently I have to trudge through all out variables for corresponding services which will take a significant amount of time. with a variable search feature i could be confident that there were no rreminaing ip references within seconds

I would also like to add - on the variable search screen I think it makes sense to search with 'contains' type queries. On a per-project basis it seems like this could be done on the client side if it is difficult to do on the database side. Thanks!

We'd find some work around variables like this really useful.

To elaborate, here are some scenarios we're finding quite difficult at the moment:

1. We want to change the name of a variable - what steps are we going to break? (particularly relevant for variable sets)

2. We have a step that uses a variable. Do we have a properly-scoped value for that variable? Is there a gap in our scoping that means it won't be replaced in some cases?