Anyone know if this causes users to become noncompliant with GDPR, FedRAMP, or similar regulatory protections?
Remove default "terraform" partner_id
31–40 of 81 posts
Re: Remove default "terraform" partner_id
#32This does indeed look bad, but I'd like to give Hashicorp the benefit of the doubt and allow them to respond before grabbing any pitchforks/torches. Let's not forget they've added a ton of value to many of our lives and have never required a cent (for the free version).
[deleted]
Re: Remove default "terraform" partner_id
#33I wonder how much the outraged individual has contributed financially to what is a fabulous tool that all DevOps engineers benefit directly from. I get that it should have been discussed, but even still - the code is there for all to see and read whenever they can be bothered too. They can even fork and build it without this. It's this level of open source snobbery that makes me think that eventually only the big com…
This sets a dangerous precedent. You shouldn't need to contribute financially to file an issue about an open source product you use. Edit: cleaned up the wording a bit by removing the "raise a concern" bit. Hopefully that removes any ambiguity in the comment.
Nowhere, in the tenets of "free software" or "open source", is there any expectation there is any mechanism whatsoever for support or even "filing issues."
If an open-source project wants to charge you money to file an issue, that's totally OK and totally in-bounds.
Re: Remove default "terraform" partner_id
#34I wonder how much the outraged individual has contributed financially to what is a fabulous tool that all DevOps engineers benefit directly from. I get that it should have been discussed, but even still - the code is there for all to see and read whenever they can be bothered too. They can even fork and build it without this. It's this level of open source snobbery that makes me think that eventually only the big com…
This sets a dangerous precedent. You shouldn't need to contribute financially to file an issue about an open source product you use. Edit: cleaned up the wording a bit by removing the "raise a concern" bit. Hopefully that removes any ambiguity in the comment.
it sounds like the perfect monetisation strategy for open source. as long as contributing a fix via a pull request is free opening a ticket to cover for the dev time needed to work on the issue in your behalf seems just fair
Re: Remove default "terraform" partner_id
#35This does indeed look bad, but I'd like to give Hashicorp the benefit of the doubt and allow them to respond before grabbing any pitchforks/torches. Let's not forget they've added a ton of value to many of our lives and have never required a cent (for the free version).
[deleted]
Re: Remove default "terraform" partner_id
#36Earlier quoted context omitted.
This sets a dangerous precedent. You shouldn't need to contribute financially to file an issue about an open source product you use. Edit: cleaned up the wording a bit by removing the "raise a concern" bit. Hopefully that removes any ambiguity in the comment.
File? No. Get worked/dealt with at all? Yeah. Developers can't feed their children with good vibes.
Pay-to-file is fine, if that's what the authors want.
Re: Remove default "terraform" partner_id
#37This is a non-issue and PURE FUD. They are anonymously tracking usage of their product on azure. BFD.
Re: Remove default "terraform" partner_id
#38Anyone know if this causes users to become noncompliant with GDPR, FedRAMP, or similar regulatory protections?
Did you read what the issue is even about? It's about setting the string "terraform" in a config file. It's not some personal data or evil tracking token.
Re: Remove default "terraform" partner_id
#39It's a random GUID that lets the company track how much their tool is used in deployments in Azure. It's about as noninvasive as it gets.
Feels sort of like a User Agent string to me.
Re: Remove default "terraform" partner_id
#40I admit I don’t closely follow Hachicorp commits, blogs, changelogs, etc.. Is it possible that there was another commit providing a rationale for the change? Maybe a changelog entry explaining what the UUID represents and how it benefits Hachicorp, Microsoft/Azure, and end users?