I have a step template with a parameter named Database.Server. When I used this step template in one of my projects I also created a variable in the project called Server.Database and then used that variable as an argument for the step templates parameter.
When deploying this results in “Variables could not be evaluated because the variable ‘Database.Server’ is cyclic: Database.Server -> Database.Server”
It makes sense of course, but it is unfortunate. It would be nice to make a step template under the “fire and forget attitude”, that is be able to create a template with whatever variable names you want and not have to worry about if there could somehow be a naming clash in one the projects that consumes the template.
For now I will adopt a more unique naming convention for my step template variables.