Scoping Variables to Only UI or Config files
I just set up a project where I created a variable called logfiles to use as a variable in a step template. I did that, and around the same time was looking at the documentation for how to do key/value pairs for web.config and I realized that I don't see a way to scope a variable to just configuration files or just the UI (or more intentionally NOT config files). My concern is that I will set a variable that ends up being a key in one of the config files and so I unintentionally update a value in the config files.
Michael Peterson
shared this idea
-
Michael Peterson
commented
To clarify the reason that I even mentioned "logfiles", is that the example documentation for Octopus mentioned "LogLevel" as a variable updated in the web.config and I found myself thinking "LogFile" sounds like something you would update in a config file somewhere. In my case, LogDir would have been a better variable name.