John Bevan

The issue seems to be down to this line: https://github.com/ebekker/ACMESharp/blob/eb110215c90b20cfe14199a0f2957496756b744a/ACMESharp/ACMESharp.Providers.IIS/IisHelper.cs#L126 I'm not sure what the logic is behind that, so haven't submitted a pull request. Perhaps simply changing this: ```...

(actually - I've made a non-breaking change; adding a parameter so people not hitting this issue can use as they do today, but those of us wishing to bypass this...

That looks correct, though you've not specified values for the `BindingAddress`, `BindingPort`, or `BindingHost` installer parameters, which differs from what I've got. Have you tried specifying those options? Please can...

Actually this is my fault... just tried the version from the PS Gallery and realised it behaved differently to my local copy / after digging around found I'd not included...

Should it help others, here's a couple of blog posts by @mcdurdin with scripts for "renewing" identifiers & certificates for a cert used by IIS: - https://marc.durdin.net/2016/11/automating-certificate-renewal-with-lets-encrypt-and-acmesharp-on-windows/ - https://marc.durdin.net/2017/02/lets-encrypt-on-windows-redux/

Similarly, if you want to search by IdP username (for us, this is the user's UPN/AAD username/email) replace `login:` with `userName:`. We use enterprise instead of organization (more here: https://stackoverflow.com/a/50614349/361842)...

For others hitting this issue, a few solutions to this error message (note: this is not an exhaustive list): ### Empty File If you create a new excel file with...

## Ordered Replacement Regarding the issue with maps not being ordered; lists are, so a simple fix for the example would be: ``` resource "resource" "resource" { name = replace(local.script,...

Thanks @jhoneill; that makes sense on reflection, & confirmed the behaviour we see exactly matches: ![screenshot showing various a foreach -parallel with a write-verbose statement where the caller's verbose switch/preference...

That makes sense; thanks @jhoneill. I guess a clean solution (though a change to how PowerShell currently works) would be for any new runtime to inherit the context of the...