Add stdinIsATTY template function

[twpayne]

Fixes #1109.

@felipecrs would you be able to test this? I'm not sure how it behaves on Windows.

[felipecrs]

Sure, let me try.

[twpayne]

Ah, you need the --init flag to chezmoi execute-template because stdinIsATTY is only available for generating the initial config file.

[felipecrs]

I realized it, sorry. I'm trying to figure out what to do to not have a stdin, to check.

[felipecrs]

Well, it doesn't work in the following scenario:

$ docker run -v c:\Users\felip\Downloads:c:\Downloads mcr.microsoft.com/windows:20H2 C:\Downloads\chezmoi.exe execute-template --init '{{ stdinIsATTY }}'
true

[felipecrs]

But surprisingly, it works like a charm when using a chezmoi init. See:

> cat .\.chezmoi.toml.tmpl
{{ $email := "" }}
{{ if stdinIsATTY }}
{{   $email = promptString "email" }}
{{ else }}
{{   $email = "[email protected]" }}
{{ end }}

[data]
    email = "{{ $email }}"
> docker run -v c:\Users\felip\Downloads:c:\Downloads mcr.microsoft.com/windows:20H2 powershell -command 'C:\Downloads\chezmoi.exe init --verbose --source C:\Downloads; C:\Downloads\chezmoi.exe data --verbose --source C:\Downloads'
{
  "chezmoi": {
    "arch": "amd64",
    "fqdnHostname": "7d2ad3306736",
    "homeDir": "C:\\Users\\ContainerAdministrator",
    "homedir": "C:\\Users\\ContainerAdministrator",
    "hostname": "7d2ad3306736",
    "kernel": null,
    "os": "windows",
    "osRelease": {},
    "sourceDir": "C:/Downloads",
    "username": "User Manager\\ContainerAdministrator",
    "version": {
      "builtBy": "goreleaser",
      "commit": "56485778b5334f3aa05b5d12abff0db00cc8cb2b",
      "date": "2021-03-28T18:30:09Z",
      "version": "v2.0.4-SNAPSHOT-5648577"
    }
  },
  "email": "[email protected]"
}
> docker run -ti -v c:\Users\felip\Downloads:c:\Downloads mcr.microsoft.com/windows:20H2 powershell -command 'C:\Downloads\chezmoi.exe init --verbose --source C:\Downloads; C:\Downloads\chezmoi.exe data --verbose --source C:\Downloads'
email? teste
{
  "chezmoi": {
    "arch": "amd64",
    "fqdnHostname": "9e5d16128b04",
    "homeDir": "C:\\Users\\ContainerAdministrator",
    "homedir": "C:\\Users\\ContainerAdministrator",
    "hostname": "9e5d16128b04",
    "kernel": null,
    "os": "windows",
    "osRelease": {},
    "sourceDir": "C:/Downloads",
    "username": "User Manager\\ContainerAdministrator",
    "version": {
      "builtBy": "goreleaser",
      "commit": "56485778b5334f3aa05b5d12abff0db00cc8cb2b",
      "date": "2021-03-28T18:30:09Z",
      "version": "v2.0.4-SNAPSHOT-5648577"
    }
  },
  "email": "teste"
}

Nonetheless, when using only docker run -t, the chezmoi still thinks the stdin is interactive, and keeps waiting for an answer (when none is possible to be inputted). But I think it's fine. It should probably be a caveat of Docker Windows containers or whatever.

> docker run -t -v c:\Users\felip\Downloads:c:\Downloads mcr.microsoft.com/windows:20H2 powershell -command 'C:\Downloads\chezmoi.exe init --verbose --source C:\Downloads; C:\Downloads\chezmoi.exe data --verbose --source C:\Downloads'
email?

[felipecrs]

If you want me to test anything, feel free to ask me. It took me a while to setup this Windows containers environment, hahaha.

[twpayne]

Thanks so much for the testing @felipecrs :)

I had no idea that Windows container environments existed. This is potentially really interesting for CI.

[felipecrs]

Yeah... the only caveat is that you need a Windows host, and the Windows docker image is around 6GB to pull. There are smaller ones, such as the Windows Nano Server (150MB), but sadly chezmoi could not run due to missing DLLs.

[twpayne]

Ah, thanks. It also looks like you need Windows 10 Pro to run Windows images, and I only have Windows 10 Home on my laptop.