PVSECRET-CREATE-ASSOCIATION(1)

💅 pvsecret-create-association — Create an association secret 🎀

okay so bestie, you know how a trusted I/O device needs to, like, link up with a guest? yeah — an association secret is literally the vibe connector for that. ✨ (and if you want the full lore, pvapconfig has the tea on association secrets, no cap)

---

🦋 SYNOPSIS

pvsecret create association [OPTIONS] <NAME>

---

🌸 DESCRIPTION

so basically: you use an association secret to connect a trusted I/O device to a guest. that's the whole point, fr fr. The pvapconfig tool provides more information about association secrets — go read it if you want the deep lore 💖

---

✨ OPTIONS ✨

• <NAME> — a string that identifies your new secret. it's giving "name tag at a party" 🎀

the actual secret is set with --input-secret. the name gets saved in NAME.yaml with white-spaces mapped to _ (yes, literally every space becomes an underscore, iconic behavior).

• --stdout — print the hashed name to stdout. 💅

heads up bestie: the hashed name is not written to NAME.yaml when you use this.

• --input-secret <SECRET-FILE> — path from which to read the plaintext secret. if you don't specify it, it just uses a random secret (surprise! 🎁).
• --output-secret <SECRET-FILE> — save the generated secret as plaintext in SECRET-FILE. 🙈

the generated secret can be used to generate add-secret requests for a different guest with the same secret using --input-secret. destroy the secret when it is not used anymore — like, for real, don't just leave it lying around, that's not the move 💀

• -h, --help — print help (see a summary with -h). easy peasy ✨

---

👀 SEE ALSO

pvsecret(1), pvsecret-create(1)

---

okay that's the whole page, bestie — go forth and associate responsibly 🫶

s390-tools · 2026-08-11 · mwah, that's the version + date sign-off, slay 💅✨🌷