search

adoptium / infrastructure

This repo contains all information about machine maintenance.
Apache License 2.0
86 stars 102 forks source link

Change Mission Statement #772

Open karianna opened 5 years ago

karianna commented 5 years ago

Some wording to indicate that we are Infrastructure as Code for other 3rd parties and that we should always make sure to be open for extension.

sxa commented 5 years ago

I'll copy in here what I said in slack on this topic :-)

"I would be nervous about doing that until we've finalised the docs on how to run it. I don't want another of these: https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/626 - it's fairly safe now (if you skip a couple of tags) and the Vagrant files are in place to make it easier to deploy in VMs but the docs aren't fully up to date and I think it still tries to change the hostname on the machine."

Once the docs are happy, and safeguards are in place, and a few people have tested them I'd be totally happy with such a change and it's definitely where we'd like to be :-)

Willsparker commented 2 years ago

The documentation around Vagrant (and PBTests) has been greatly worked on since the latest comment. I believe (from my look at the wikipedia article) that we are 'infrastructure as code', so I don't think it's unreasonable to put it in the docs now :-)