Can I bootstrap with one command if I use 1Password in init?

[jdevera]

I followed the docs and set up my 1Password installer as a hooks.read-source-state.pre hook.

However, I failed to pay enough attention to the very start of the docs where it says (emphasis mine):

If you use a password manager to store your secrets then you may need to install your password manager after you have run chezmoi init on a new machine but before chezmoi init --apply or chezmoi apply executes your run_before_ scripts.

I'm bootstrapping with sh -c "$(curl -fsLS get.chezmoi.io/lb)" -- init --apply jdevera and wonder if there is a way to make chezmoi run something before init.

Currently, I get this:

chezmoi: template: chezmoi.toml:92:14: executing "chezmoi.toml" at <onepasswordRead (printf "%s/email" $identity_entry)>: error calling onepasswordRead: op signin --raw: exec: "op": executable file not found in $PATH

[twpayne]

See https://www.chezmoi.io/user-guide/advanced/install-your-password-manager-on-init/.

[twpayne]

Oh wait, you already read that. Let me think...

[twpayne]

[I] wonder if there is a way to make chezmoi run something before init.

At a first glance, no, because before chezmoi init, chezmoi has not had a chance to download any of your personal configuration.

[jdevera]

The failure happens from my chezmoi.ini.tmpl file, which contains a call to onepasswordRead. But this means that my files are already present and being read, while the script has not been called yet. So I guess the chezmoi.toml.tmpl does not count as source state for the purpose of the hook?

[twpayne]

There's a chicken-and-egg problem here. chezmoi has to execute your config file template (chezmoi.ini.tmpl) before it can read your config file (the generated chezmoi.ini) and know what hooks to run.

#664 is relevant.

In the short term, the fix is to not to include calls to your password manager in your config file template. Why, exactly, do you need to do this?

[jdevera]

In the short term, the fix is to not to include calls to your password manager in your config file template. Why, exactly, do you need to do this?

I am using it to load personal details that will depend on the machine but do not change across runs.

I understand that, if I move this to a separate data file this will be re-evaluated in every apply, is this correct?

[jdevera]

I can also suggest having an option for init that can take the hook in the command line as a way to break out of the chicken and egg problem.

Something like:

sh -c "$(curl -fsLS get.chezmoi.io/lb)" -- init --apply --pre-init .foo.sh jdevera

Where .foo.sh could be relative to the chezmoi home dir.

[twpayne]

I suspect that you're correct here, and that --pre-init is potentially a nice solution. I need to think about it for a bit though.

[Lockszmith-GH]

While in actuality a double init, I have performed an automated follow-up init after an initial initialization run in #4415

[jdevera]

This is intriguing, but I'm already planning a multi-level setup to track work and personal files separately and am very wary of creating a massive stack of chezmoi, I'll have to call it the apartment building :)

[Lockszmith-GH]

Empire state