[13] Can the 1Password CLI replace dotenv (on Raspberry Pi)?

I'm running all kinds of services, scripts and other automations on my desktop and my NAS. All of those would benefit from integrating with 1Password, instead of having credentials to email accounts (and other accounts) in plain text or encrypted using a convoluted process which requires some work if I were to change a password somewhere. If I could use 1Password for this I'd only need to update the password(s) in 1Password and the scripts would just keep on running without issues.

At the moment it's just me in my family who would be using this, partly because I've not been able to get more people on board the password manager train (something I think many here can relate to) and the pandemic didn't make it any easier. But with time I expect there to be more who'll join our family account who'd want (or need) to use these kind of features. I could help them automate some thing(s) at their place and teach them how to troubleshoot when something goes wrong and put the documentation in 1Password. Then they'd have their own service account(s) to manage and could contact me if there's an issue they couldn't resolve by themselves.

My closest family are spread out in different cities and if I manage to reach my goal of getting everyone on board 1Password, then we'd be a bunch of Family Organizers, of which a smaller group work in IT in some capacity and who would benefit from being able to use 1Password for more than just storing credentials. Let's say we have some automation that requires a script to be run locally at each person's home but the script should leverage the same credentials. If the script references credentials in 1Password, then we can store those in a shared vault and edit those whenever needed without needing to update the script.

In 1Password Families you're either a member or a organizer, so either a regular user or a global admin. There's no granularity there (I wish there was), so I'm guessing creating and managing service accounts will only be possible for Family Organizers, just like for the other account types? In any case, it would be nice to automate the storing of the credentials for the service accounts somehow. Like if you create a service account, a login item gets created with it and it would either be stored in the creator's private vault by default, or there could be a modal with a question of where to store it. You could then move the login item around between vaults as you please, but, if possible, there could be a permanent link between the service account and the login item, so if you change the password for the account, the password stored in the login item gets updated automatically. Or perhaps creating a service account should work like many services handle API keys; you only get to see the credential(key) when the account is created and it's up to you if you want to store it and where, and if you need to replace it, you either generate a new credential or create a new service account and remove the old one.