You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd suggest using the ci/cd implementation to store the entire config file as the secret and have the workflow write it in place.
Depending on where you're running this, you could use the k8s secret management to do something similar and map in the config file to a pod on a cron-job that runs the script as well.
If you're looking for more specific help, you'll likely need to provide more information about your setup since even the 1Password docs fork their docs based on if you use a Connect server or not, which you didn't mention: https://developer.1password.com/docs/secrets-automation/
Introducing 1Password Secrets Automation workflows. Use a 1Password Service Account or Connect server to secure, orchestrate, and manage your infrastructure secrets.
There is a Connect Server in place and I want to use Platypus to bundle the .conf (and/or .env file) in the .app build which then calls for the injection of the secrets every time the app runs.
Can somebody point me into the right direction to implement the use of 1Password Secrets?
Thanks!
The text was updated successfully, but these errors were encountered: