(Not a legal advice) AFAIK, they can’t. If you want to switch a license you have to get consent of all contributors or (in case of CLA shit) consent of the owner of the code
There’s plenty of responses which are probably more thorough than I am, however, as I understand it as a PM dealing with cloud migrations:
Terraform is scripts of code which automates the deployment cloud platforms, applications, services so that you don’t need to manually set up and configure everything each time.
You like deploying infrastructure, probably in a cloud environment, but you don’t want to push a bunch of buttons in their web interface, so you use Terraform to declaratively define the things you want, and it goes and builds them for you. Super useful for when you need to build resources often, to detect and correct config drift, and get started down the path of Infrastructure as Code.
In the past you would stand up and hand-configure all of the hardware that would run your software. This is a way to define the hardware configuration in software and apply it automatically. Advantages of this approach include increased scalability, reproducibility, and being able to use version control.
Plus, it is idempotent, which means you don’t have to change it before pushing it to an existing infrastructure. If you do change it, the infrastructure will be updated to match. It ends the need for custom deployment scripts.
Pulumi looks cool but unfortunately I haven’t seen a single company advertising Pulumi as a desirable skill, so if I wanted to land a job in this area, I’d still be forced to learn Terraform.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Nice, but I wonder if they plan to switch to GPL, or stay with MPL. No mention of that on the website.
They probably won’t GPL it, since that’ll make the fork even less appealing to companies.
(Not a legal advice) AFAIK, they can’t. If you want to switch a license you have to get consent of all contributors or (in case of CLA shit) consent of the owner of the code
The MPL allows for it as far as I can tell, its just fairly complicated since the MPL would still apply at the file-level for all existing files.
I googled but I can’t understand what’s terraform, can someone eli5?
I don’t use it or cloud stuff.
But it looks like it’s a tool to make it easier to manage how you put all the different pieces of cloud hosting together.
There’s plenty of responses which are probably more thorough than I am, however, as I understand it as a PM dealing with cloud migrations:
Terraform is scripts of code which automates the deployment cloud platforms, applications, services so that you don’t need to manually set up and configure everything each time.
You like deploying infrastructure, probably in a cloud environment, but you don’t want to push a bunch of buttons in their web interface, so you use Terraform to declaratively define the things you want, and it goes and builds them for you. Super useful for when you need to build resources often, to detect and correct config drift, and get started down the path of Infrastructure as Code.
Yeah it works super well if you have a base config across all nodes then you want to create per project configs and spin them off your build system.
Infrastructure as Code
In the past you would stand up and hand-configure all of the hardware that would run your software. This is a way to define the hardware configuration in software and apply it automatically. Advantages of this approach include increased scalability, reproducibility, and being able to use version control.
Plus, it is idempotent, which means you don’t have to change it before pushing it to an existing infrastructure. If you do change it, the infrastructure will be updated to match. It ends the need for custom deployment scripts.
After switching to Pulumi, I don’t ever want to use terraform again
Pulumi looks cool but unfortunately I haven’t seen a single company advertising Pulumi as a desirable skill, so if I wanted to land a job in this area, I’d still be forced to learn Terraform.
Anything Hashicorp is just junk. It might work, but still junk under the covers. I never want to work with vault, consul, terraform, etc ever again.