Patrick de Ruiter
22d78bf85c
All checks were successful
Code Quality & Security Scan / TFLint (push) Successful in 24s
Code Quality & Security Scan / Tfsec Security Scan (push) Successful in 30s
Code Quality & Security Scan / Checkov Security Scan (push) Successful in 44s
Code Quality & Security Scan / Terraform Validate (push) Successful in 43s
Code Quality & Security Scan / SonarQube Trigger (push) Successful in 47s
- Remove ansible/ from .gitignore - Add vault_agent role (copied from terraform-vsphere-infra) - Add vault_agent-playbook.yml for deployment - Include ansible collections (cloud.terraform, ansible.posix, etc.) - Archive consul_template role as consul_template-legacy The ansible directory contains the vault-agent deployment automation that replaces the legacy consul-template approach.
15 lines
1.1 KiB
Plaintext
15 lines
1.1 KiB
Plaintext
|
|
License for CIS Controls:
|
|
|
|
Creative Commons License
|
|
|
|
This work is licensed under a Creative Commons Attribution-NonCommercial-No Derivatives 4.0 International
|
|
Public License (the link can be found at https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode.
|
|
To further clarify the Creative Commons license related to the CIS Controls® content, you are authorized to
|
|
copy and redistribute the content as a framework for use by you, within your organization and outside of your
|
|
organization, for non-commercial purposes only, provided that (i) appropriate credit is given to CIS, and (ii)
|
|
a link to the license is provided. Additionally, if you remix, transform, or build upon the CIS Controls, you may
|
|
not distribute the modified materials. Users of the CIS Controls framework are also required to refer to (http://
|
|
www.cisecurity.org/controls/) when referring to the CIS Controls in order to ensure that users are employing
|
|
the most up-to-date guidance. Commercial use of the CIS Controls is subject to the prior approval of the
|
|
Center for Internet Security, Inc. (CIS®). |