Chris Hunt

I've started a [branch ](https://github.com/Ticketmaster/poshspec/tree/feature_remoting) to work on remote execution support. My plan is to use `Invoke-Command` to handle the remote execution. That way it is handled consistently module wide...

@devblackops The goal was to get a lot of the logic outside of the scope of the Pester functions to enable testing. The parsing of the scriptblock replaces the variables...

I assumed the value in the Should block would be a constant, but it should be possible to expand variables with `$ExecutionContext.InvokeCommand.ExpandString()` the same way we do on the other...

I just tested adding `$assertion = $ExecutionContext.InvokeCommand.ExpandString($assertion)` to Get-PoshSpecParam and it works with one caveat, the variable must be defined in Global scope. The way you solved it works really...

I've changed the default release behavior to draft instead of publish. The notes will auto-generate to an extent based on PR title, but will still need hand editing. It's difficult...

Opened https://github.com/goreleaser/goreleaser/issues/2780 to get some help with the extra "What's Changed" text appearing in the notes.

Replaced by #1682

Sorry for the slow response. The docker image does have `dnscontrol` as the `entrypoint`. You should be able to pass arguments as part of the `docker run cmd`. eg `docker...

I've done very little with AWS hosted DNS and never with Private zones, but my thought would be to use `D()` since it is technically a different zone.

@m-ueberall I think you could simplify this workflow by using https://github.com/mitchellh/gox.