Hi Wido, means its community driven in the future?
What i know terraform was not up to date for cs in the last years. Cheers Sven __ Sven Vogel Lead Cloud Solution Architect EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke Registergericht: Leipzig HRB 9065 Support: +49 341 42649 555 Zertifiziert nach: ISO/IEC 27001:2013 DIN EN ISO 9001:2015 DIN ISO/IEC 20000-1:2018 ISAE 3402 Typ II Assessed EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<https://www.linkedin.com/company/ewerk-group> | Xing<https://www.xing.com/company/ewerk> | Twitter<https://twitter.com/EWERK_Group> | Facebook<https://de-de.facebook.com/EWERK.IT/> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. Disclaimer Privacy: Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank. The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you. Von: Wido den Hollander <w...@widodh.nl> Datum: Mittwoch, 27. Januar 2021 um 11:06 An: Niclas Lindblom <niclas_lindb...@icloud.com>, us...@cloudstack.apache.org <us...@cloudstack.apache.org> Cc: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Betreff: Re: [DISCUSS] Terraform CloudStack provider On 1/27/21 12:18 AM, Niclas Lindblom wrote: > I can confirm that the Terraform plugin is working if it is already > installed, since it was archived it no longer automatically downloads when > applying unless manually installed. > > From the Hashicorp website, it appears it was archived when they moved all > plugins to their registry and needs an owner and an email to Hashicorp to be > moved into to the registry and supported again when running Terraform. I use > it regularly but haven’t got the technical skills to maintain the code so > been hoping this would be resolved. > I mailed Hashicorp to ask about this: "Thanks for reaching out. The provider was archived because we launched the Terraform Registry last year which allows vendors to host and publish their own providers. We'd be happy to work with you to transfer the repository over to a CloudStack Github organization where you can build and publish releases to the registry. We'd also like to have CloudStack join our Technology partnership program so I can mark your Terraform provider as verified." So I think we don't need to do much technology-wise. I don't use Terraform and don't have a major stake in it, but I would hate to see the Provider being removed from Terraform. Should we request https://github.com/apache/cloudstack-terraform at infra and then host the Provider there? Wido > Niclas > >> On 26 Jan 2021, at 18:33, christian.nieph...@zv.fraunhofer.de wrote: >> >> >> >>> On 26. Jan 2021, at 10:45, Wido den Hollander <w...@widodh.nl> wrote: >>> >>> >>> >>> On 1/26/21 10:40 AM, christian.nieph...@zv.fraunhofer.de wrote: >>>> On 25. Jan 2021, at 12:40, Abhishek Kumar <abhishek.ku...@shapeblue.com> >>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> Terraform CoudStack provider by Hashicorp is archived here >>>>> https://github.com/hashicorp/terraform-provider-cloudstack >>>>> >>>>> Is anyone using or maintaining it? >>>> >>>> We are also using it heavily and are somewhat worried about the module >>>> being archived. >>> >>> Agreed. But do we know why this has been done? What needs to be done to >>> un-archive it? >>> >>> If it's just a matter of some love and attention we can maybe arrange >>> something. >>> >>> Is it technically broken or just abandoned? >> >> This is just an educated guess, but given that we're not experiencing any >> technical issues, I believe it has just been abandoned. >> >> Christian >> >> >>> >>> Wido >>> >>>> >>>>> We're aware of Ansible CloudStack module >>>>> (https://docs.ansible.com/ansible/latest/scenario_guides/guide_cloudstack.html) >>>>> but are there any other alternatives of Terraform that you may be using >>>>> with CloudStack? >>>> >>>> The ansible module is working quite well. However, one of the advantage of >>>> terraform imho is that one can easily destroy defined infrastructure with >>>> one command, while with ansible 'the destrcution' needs to be implemented >>>> in the playbook. Another advantage is that (at least) Gitlab can now >>>> maintain terraform states, which quite nicely supports GitOps approaches. >>>> >>>> Cheers, Christian >>>> >>>>> >>>>> Regards, >>>>> Abhishek >>>>> >>>>> abhishek.ku...@shapeblue.com >>>>> www.shapeblue.com<http://www.shapeblue.com> >>>>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK >>>>> @shapeblue >>>>> >>>>> >>>>> >>>> >> >
