How to make sure 1Password Connect is up and running before invoking op commands?

XIIIXIII
Community Member
edited March 17 in Secrets Automation

My main reason for using 1Password Connect is to replace .env files with credentials in plain text.

These are mostly used by Node.js scripts that I start as services using systemd on a Raspberry Pi.

I was planning to use systemd's Wants/Requires and Before/After syntax to make sure these scripts/services will only run once 1Password Connect is up and running.

Unfortunately, I noticed (using journalctl -f -u 1password-connect after executing systemctl restart 1password-connect) that it takes quite some time after invoking (ExecStart=) docker-compose up (in the 1password-connect service) before I can (successfully) use the op command.

How to make sure 1Password Connect is up and running before invoking op commands?

(in scripts started as systemd services?)

Comments

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file