Live data from Hacker News

IBM completes acquisition of HashiCorp

newsroom.ibm.com

91–100 of 407 posts

Re: IBM completes acquisition of HashiCorp

#91

Earlier quoted context omitted.

> For Terraform (at least a few years ago) a badly reviewed PR could cause catastrophic data loss because resources are deleted without requiring an explicit tombstone. There have been lifecycle rules in place for as long as I can remember to prevent stuff like this. I'm not sure this is a "problem" unique to terraform.

What happens if you forget the lifecycle annotations or put them in the wrong place or you accidentally delete them? Last time I checked it was data loss, but that was a few years ago.

The same as in any other language when what you wrote was not what you intended? Sorry, I’m really confused what your complaint here is or how you’d prefer it to work. If you make a sensitive resource managed by any kind of IAC, of course the IAC can destroy it in a manner that would result in irretrievable data loss. The language has for forever put semantics in place to prevent that, and I’m not sure as a power user I’d want it any other way, I’m explicit with what I want it to do and dont want it making crazy assumptions that I didnt write.

like, what happens if you forget to free a pointer in c? sorry for snark but there are an unbelievably numerous amount of things to complain about in tf, never heard this one.

Re: IBM completes acquisition of HashiCorp

#95
post #68

Earlier quoted context omitted.

We experienced arbitrary layoffs in 2023, followed by an ominous feeling that more layoffs were imminent. However, the announcement of a deal changed the situation. Now, we are actively hiring for numerous positions. Personally, I am not planning to stay much longer. I had hoped that our corp structure would be similar to RedHat, but it seems that they intend to fully integrate us into the IBM mothership.

Red Hat has been a very atypical approach. There has been some swapping of teams back and forth but, as far as I can tell (been out of it for a while), Red Hat is still quasi-independent. Still lots of changes (probably most notably because of a lot of growth) but strategic Red Hat areas still seem to be pretty independent.

> Red Hat is still quasi-independent. Still lots of changes (probably most notably because of a lot of growth) but strategic Red Hat areas still seem to be pretty independent.

Still broadly correct.

Re: IBM completes acquisition of HashiCorp

#96

Earlier quoted context omitted.

What happens if you forget the lifecycle annotations or put them in the wrong place or you accidentally delete them? Last time I checked it was data loss, but that was a few years ago.

The same as in any other language when what you wrote was not what you intended? Sorry, I’m really confused what your complaint here is or how you’d prefer it to work. If you make a sensitive resource managed by any kind of IAC, of course the IAC can destroy it in a manner that would result in irretrievable data loss. The language has for forever put semantics in place to prevent that, and I’m not sure as a power use…

[dead]

Re: IBM completes acquisition of HashiCorp

#97

Earlier quoted context omitted.

> For Terraform (at least a few years ago) a badly reviewed PR could cause catastrophic data loss because resources are deleted without requiring an explicit tombstone. There have been lifecycle rules in place for as long as I can remember to prevent stuff like this. I'm not sure this is a "problem" unique to terraform.

What happens if you forget the lifecycle annotations or put them in the wrong place or you accidentally delete them? Last time I checked it was data loss, but that was a few years ago.

I mean its also data loss if you run DROP DATABASE when you shouldn't. thats not sqls fault

Re: IBM completes acquisition of HashiCorp

#99
post #8

Earlier quoted context omitted.

That's true, but it's easier to switch from Terraform to Pulumi than it is to move from VMware to some other virtualization platform.

secrets, too. Org's already knee deep in vault / vault-agent for PKI and secrets wont be eager to switch.

But vault was already a pretty enterprise offering. I'd imagine most people running it had an existing contract.

Re: IBM completes acquisition of HashiCorp

#100

Earlier quoted context omitted.

What happens if you forget the lifecycle annotations or put them in the wrong place or you accidentally delete them? Last time I checked it was data loss, but that was a few years ago.

The same as in any other language when what you wrote was not what you intended? Sorry, I’m really confused what your complaint here is or how you’d prefer it to work. If you make a sensitive resource managed by any kind of IAC, of course the IAC can destroy it in a manner that would result in irretrievable data loss. The language has for forever put semantics in place to prevent that, and I’m not sure as a power use…

> what happens if you forget to free a pointer in c?

Assuming you mean 'forget' to free malloc'd space referenced by at least one pointer, that's an easy one .. it's reclaimed by the OS when the process ends.

Whether that's a bad thing or not really depends on context - there are entire suites of interlocked processing pipelines built about the notion of allocating required resources, throughputing data, and terminating on completion - no free()'s

Post reply on HN