Closed gvee-uk closed 2 years ago
The ability to mark SSIS environment variables as sensitive previously existed in an old version of this solution, but is no longer present.
This was pulled out because it was hitting a not-so-memorable issue that occurred either:
So, I guess what I'm saying is, adding this back in should be trivial, but you have to prove that it works correctly post-deployment!
Not entirely sure what the previous error was. I've tweaked the [obviously] incorrect code (see PR #45) and this appears to "just work".
The ability to mark SSIS environment variables as sensitive previously existed in an old version of this solution, but is no longer present.
This was pulled out because it was hitting a not-so-memorable issue that occurred either:
So, I guess what I'm saying is, adding this back in should be trivial, but you have to prove that it works correctly post-deployment!