From: "Chuck Wolber" <chuck@wolber.net>
To: <yocto@lists.yoctoproject.org>, <seth.raymond@matrixspace.com>,
"Alexander Kanavin" <alex.kanavin@gmail.com>
Subject: Re: [yocto] Documentation around adding custom fetchers to layer
Date: Sun, 21 Sep 2025 21:22:31 +0000 [thread overview]
Message-ID: <DCYSLBD104MG.18TCJAXRPR4ZS@wolber.net> (raw)
In-Reply-To: <27586.1758120354644994131@lists.yoctoproject.org>
On Wed Sep 17, 2025 at 2:53 PM UTC, seth.raymond via lists.yoctoproject.org wrote:
>
> Sure, I can share the source. It grabs secrets from our password manager
> (1Password) and injects them into the build system. We currently have two use
> cases for this:
It is probably worth noting that the 1Password v8 CLI and SDK both require a
round trip to the cloud even if you run the desktop 1P client locally (which
maintains a local copy of your vaults). The 1P CLI and SDK do _some_ caching,
but they still require a round trip for every call. My testing has shown that
this round-trip adds about a second when taking full advantage of what they
cache locally.
For a tool meant to help with automation, this falls into the "egregious"
category of oversights as far as I am concerned. After 12 years of 1P use, I am
actively exploring other options.
..Ch:W..
next prev parent reply other threads:[~2025-09-21 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 20:04 Documentation around adding custom fetchers to layer seth.raymond
2025-09-17 9:14 ` [yocto] " Ross Burton
2025-09-17 9:19 ` Alexander Kanavin
2025-09-17 14:45 ` seth.raymond
2025-09-18 7:58 ` Alexander Kanavin
2025-09-18 13:25 ` seth.raymond
2025-09-21 21:22 ` Chuck Wolber [this message]
2025-09-17 22:33 ` [bitbake-devel] " Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DCYSLBD104MG.18TCJAXRPR4ZS@wolber.net \
--to=chuck@wolber.net \
--cc=alex.kanavin@gmail.com \
--cc=seth.raymond@matrixspace.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.