Floris,
On Sat, Apr 21, 2018 at 10:50 AM, Floris Bruynooghe wrote:
>
> One downside I see with doing this is that it's a fair amount of
> complexity which mostly only you will understand and be able to
> maintain. I'm not sure the current maintenance overhead of doing things
> by hand warrants
Hi Ringo,
On Fri 20 Apr 2018 at 08:26 +0200, Ringo De Smet wrote:
> If you want, I can get you bootstrapped on this Terraform setup. I can say
> I almost know Terraform inside out. ;-)
Thanks for the offer to help with the project!
One downside I see with doing this is that it's a fair amount of
Thank you Ringo,
I have no immediate plans to implement something like this but I would
definitely appreciate some further docs/explanations/blog that unravels how
it is accomplished.
Cheers,
Oliver
On Fri 20. Apr 2018 at 08:26, Ringo De Smet
wrote:
> Floris, Oliver,
>
> If you want, I can get
Floris, Oliver,
If you want, I can get you bootstrapped on this Terraform setup. I can say
I almost know Terraform inside out. ;-)
Ringo
On Thu, Apr 19, 2018 at 9:17 PM, Oliver Bestwalter
wrote:
> Hi,
>
> Floris wrote:
> > That's a nice bit of automation.
>
> I like the idea that it works some
Hi,
Floris wrote:
> That's a nice bit of automation.
I like the idea that it works somehow, but after looking at the README it
is still undistinguishable from magic to me.
Floris wrote:
> [0] Bonus points for whoever contributes a teams functionality to
warehouse!
This is why I think that this
On Thu 19 Apr 2018 at 13:28 +0200, Ringo De Smet wrote:
> Floris,
>
> Let me pass on how other communities manage Github teams, repositories and
> shared maintenance. Here is the example from the Chef (config management
> tool) community:
>
> https://github.com/sous-chefs/terraform-github-org
>
>
Floris,
Let me pass on how other communities manage Github teams, repositories and
shared maintenance. Here is the example from the Chef (config management
tool) community:
https://github.com/sous-chefs/terraform-github-org
They have everything scripted with Terraform[1] in a public read only re
Hi all,
While just looking at
https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
I had some observations:
1. It says one of the objectives of having plugins under pytest-dev is
"Sharing some of the maintenance responsibility (in case a maintainer
