Earlier quoted context omitted.
The BSL licensing thing has turned off a lot of the more hobbyist/tinkerer-centric users who really rocketed HashiCorp's products up the ladder in their orgs. It's a bit like Elasticsearch, I think—it's gotten big enough it won't be a quick death, but I don't see Hashi's products growing/dominating as much now as I did a couple years ago. (As an aside, I'd like to thank Mitchell for his work over the years, Vagrant e…
It's true that the licensing change is a turnoff, but Terraform redefined an industry. What's the alternative? (I'm hoping Mitchell is going to have an answer to that)
Mitchell reflects as he departs HashiCorp
121–130 of 192 posts
Re: Mitchell reflects as he departs HashiCorp
#122Earlier quoted context omitted.
KMS? Secrets manager? Are those offered by a particular vendor or what
Yes but if you want to be multi-cloud and not have to integrate with each cloud's secret storage API, you would do it once for Vault and bring it with you to each cloud.
If I'm building product for on prem I'd prefer to use env vars or k8s secrets and let the customer integrate their preferred secrets manager. Also helpful when you run sales POCs where ease of getting to splash page really matters.
Building inside enterprise, I've never actually had to support multiple clouds for the same component but if it ever comes up and I have any sort of choice in the matter I would probably rather template 3 native secrets integrations than deal with the special circle of hell that is enterprise-managed Vault or CyberArk.
Re: Mitchell reflects as he departs HashiCorp
#123Earlier quoted context omitted.
KMS? Secrets manager? Are those offered by a particular vendor or what
Yes but if you want to be multi-cloud and not have to integrate with each cloud's secret storage API, you would do it once for Vault and bring it with you to each cloud.
Also my vision of multi-cloud in large org hasn't been that a particular product/app or team was ever using multiple clouds. My experience is that large orgs like to have multi-cloud support because they grow by acquiring other companies regardless of which cloud vendor they are using so you just want to provide standards and templates for everyone. Obviously said templates will be usually cloud vendor specifics.
Re: Mitchell reflects as he departs HashiCorp
#124Re: Mitchell reflects as he departs HashiCorp
#125We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.
Re: Mitchell reflects as he departs HashiCorp
#126We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.
Re: Mitchell reflects as he departs HashiCorp
#127We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.
My first major foss was heavily based around Vagrant (PuPHPet). It was a joy building on top of your tooling to make web engineers lives easier. Thank you for your work, it was great while it lasted!
I actually still have some projects with a Vagrant VM based on it that I have to move to docker compose or something.
Re: Mitchell reflects as he departs HashiCorp
#128Out of topic but I can't help to notice the og:image of the web page is 57 MiB. https://www.datocms-assets.com/2885/1702507860-mitchell-hc19...
Re: Mitchell reflects as he departs HashiCorp
#129We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.
Re: Mitchell reflects as he departs HashiCorp
#130We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.