terraform-provider-marathon
terraform-provider-marathon copied to clipboard
nicgrayson
consider moving to terra-farm or core?
I don't know if marathon is ready to start joining core, but if it is I'd like to help with the process.
If we want to not actually be in core, some folks are putting together an org like sous-chefs does for chef cookbooks. Then maintainers can help each other out reviewing, merging and releasing changes. The main advantage is having more than one maintainer who can pass the torch. If that sounds interesting, the conversation is happening at https://github.com/terra-farm/meta/issues
If that doesn't sound ideal, please let me know!
Hi, @josephholsten @nicgrayson now that the required providers will be automatically installed during terraform init (https://github.com/hashicorp/terraform/blob/v0.10.0/CHANGELOG.md) it would make a lot of sense to try to get this into https://github.com/terraform-providers.
Anyone know how you get projects moved to https://github.com/terraform-providers?
@nicgrayson mostly it requires a set of acceptance tests, a maintainer, and a poke of hashicorp. I'll go take care of the last bit!
@josephholsten after having a chat with @luisdavim, i feel like https://github.com/terra-farm/meta and https://github.com/terraform-providers are different entities, can you confirm that?
Luis also said that this issue is older than terraform-providers exists and terraform-providers seems to be a better place to give ownership of the repo.
Terra-Farm is definitely different from terraform-providers. Unless you have a good reason to stay outside the hashicorp approved providers, terraform-providers is the best place to be!
Maybe @apparentlymart could help. There's a fork that is more up to date at https://github.com/ContainerLabs/terraform-provider-marathon we're actually forking that one because the guys at ContainerLabs are more responsive and proactive handling PRs.
@luisdavim the ContainerLabs repo no longer exists. Do you have any idea where that fork went? Are all contributions to that fork lost now?
Hi all!
The process for being in terraform-providers is documented in Terraform Provider Development Program.
That process is primarily intended to handle the situation where a vendor is implementing a Terraform provider for their own product. It's quite heavyweight for a community-maintained provider, so an organization like terra-farm could be a better compromise.
While at the moment only providers from terraform-providers can be automatically installed by terraform init, there is work in progress on opening that up in a later release. Making Terraform v0.12.0 install providers via an index on registry.terraform.io was the first step for that, and generalizing that to support other GitHub organizations/accounts will follow in a subsequent release.
The Terraform issue representing that work is hashicorp/terraform#15252, if you'd like to follow it for updates.
