Infrastructure as code (IaC) is the definition of managing and provisioning computer resources through configuration files rather than physical hardware configuration. With IaC, you can configure files that include the specifications of your infrastructure, facilitating the edition and distribution of your environment configurations. It also ensures that you provide the same environment every time.
All configuration files must belong to the source like any other software source code. By deploying the infrastructure as code, you can organize your code into modules and combine them in different ways through automation.
This way, by automating IaC provisioning, developers don't have to manually provision and manage servers, operating systems, storage, and other infrastructure components every time they build or deploy an application.
[X] Create a VM
[X] All provisioning must be done in a bash script-type file
[X] The user root will be the owner of all created directories
| DIRECTORIES | GROUPS | USERS |
|---|---|---|
| /public | all groups | all users |
| /adm | GRP_ADM | carlos, debora, josefina |
| /ven | GRP_VEN | maria, sebastiana, amanda |
| /sec | GRP_SEC | joao, roberto, rogerio |
[X] All users have full permissions on the public directory
| user | /public | /adm | /ven | /sec |
|---|---|---|---|---|
| root | owner | owner | owner | ownner |
| GRP_ADM (carlos, debora, josefina) | w, r, x | w, r, x | ||
| GRP_VEN (josefina, sebastiana, amanda) | w, r, x | w, r, x | ||
| GRP_SEC (joao, roberto, rogerio) | w, r, x | w, r, x |
[X] Users of each group have full permissions within the respective directory referring to the department they are part of
[X] An user cannot read, write or execute permissions on directories of departments that they do not belong to
[X] Tag Denilson on Linkedin
This project is under an GNU General Public License v3.0. See more details in LICENSE for more information.