Actual benefits are non-stated

[serious-angel]

Dear JonMagic,

Thank you for the opinions shared.

---

The work I am writing about is the following: Stop Putting Secrets in .env Files.

I am not sure how it's better to store and even transfer credentials back and forth through some third-party as 1Password:
- https://developer.1password.com/docs/ci-cd/github-actions#usage-examples

I am sorry, but the actual benefits are non-stated, and it feels like an ad for 1Password, to be frank.

---

Best and kind regards

[jonmagic]

Appreciate the feedback. Funny enough I just switched to keychain for my main use case after posting this and getting some feedback from a coworker. I may update the post tomorrow after I've thought on the first part of your response overnight.

[jmeridth]

@serious-angel There is a whole section stating what you gain. 1Password is a great password manager and it is the one @jonmagic is using, hence the content. If you use another password manager, look up their CLI and see if you can do the same thing.

Note: I've used many password managers in my life and 1Password is currently my favorite. That can change.

@jonmagic thanks for a great post.

[serious-angel]

I read the "what you gain", yet there's nothing about anything gainful I see, sorry, and "hence the content".

To clarify, I do realize that the appreciated article required time and effort to invest into, but I just do not see the benefits nor I agree with the approach. Why should I or anyone use a personal password manager at non-personal enterprise environment, that is at deployment on production VPS/VDS/hosting servers, container clusters, or other temporary machinery at data centers? No only that, but associate it with a yet another third-party? At this point, you should have considered implementations similar to:
- Vault by DotEnv;
- Vault by HashiCorp.