Our team has now had to fork this and host it internally to avoid InfoSec's designation as protestware, as well as corporate policies regarding political positions and the nationality component of our DEI initiatives -- our Russian engineers were the ones who identified this as problematic.
It's absolutely your choice to do so, but we find it highly inappropriate. You may disagree, as is your right, but you have ultimately degraded this module's usefulness and appeal in enterprise settings, where Terraform is leveraged all over the place. You've rendered your work radioactive in several quarters.
Apparently we now have to curate the Terraform registry. We already scan SBOMs to keep these things out of NodeJS, Java, etc. projects.
I strongly urge you to strip the politics out of the module code.
[X] ✋ I have searched the open/closed issues and my issue is not listed.
Description
Our team has now had to fork this and host it internally to avoid InfoSec's designation as protestware, as well as corporate policies regarding political positions and the nationality component of our DEI initiatives -- our Russian engineers were the ones who identified this as problematic.
It's absolutely your choice to do so, but we find it highly inappropriate. You may disagree, as is your right, but you have ultimately degraded this module's usefulness and appeal in enterprise settings, where Terraform is leveraged all over the place. You've rendered your work radioactive in several quarters.
Apparently we now have to curate the Terraform registry. We already scan SBOMs to keep these things out of NodeJS, Java, etc. projects.
I strongly urge you to strip the politics out of the module code.