Share this post:
Developers do not like to write the same thing twice. The DRY principle is one example of this. Similarly they don’t like having to go through tons of clicks in a user interface to setup an environment. Consequently shell scripts have been long used by system administrators and developers to automate repetitive, error-prone and uninteresting tasks.
Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Container as a Service (CaaS), Functions as a Service (FaaS) have given developers high level of abstraction and it became easier to acquire resources like bare metal servers, managed databases, virtual machines, Kubernetes clusters, etc. But once you have provisioned these resources, you need to connect them together, to configure user access, to update the configuration over time, etc. Being able to automate all these steps and to repeat the installation, configuration under different environments is a must-have these days.
Multiple environments are pretty common in a project to support the different phases of the development cycle with slight differences between the environments like capacity, networking, credentials, log verbosity. How could we automate the creation of these environments? What tools could we use?
We have added a new tutorial to the IBM Cloud documentation where we look at questions and use tools like the IBM Cloud CLI and the IBM Cloud provider for Terraform to automatically provision resources.
The tutorials section has a feedback form on the side where you can comment on the content. If you have suggestions on the existing tutorials or ideas for future additions, please submit your feedback.
via IBM Cloud Blog https://ibm.co/2pQcNaA
April 10, 2018 at 11:06AM