Closed dlemstra closed 2 months ago
In case it helps: On the public preview announcement, the team reported the reasoning for keeping the deprecated naming was to avoid breaking compatibility for the people who were on the private preview.
Perhaps some logic could be added so that both the old/new naming schemes would work?
Sounds like a good idea to allow both names and raise a warning when the old name is used?
Thank you for pointing this out. I tried so hard to rename everything and just completely overlooked this.
Sounds like a good idea to allow both names and raise a warning when the old name is used?
I like this idea. Would you like to open a PR? If not, I'll get to it when I have time.
I have created this PR: #14. When will you publish the powershell module on GitHub so we (me) can do the same there?
It might be a good idea to rename
code-signing-account-name
totrusted-signing-account-name
? And it also looks like the readme could use an update in the option descriptions.