generic cloud init help and docs
treats user data and cloud init as cloud-init
| # Create kv-policy with variable for Identity Group ID | |
| data "vault_policy_document" "group" { | |
| rule { | |
| path = "group-kv/data/training/{{identity.groups.ids.${vault_identity_group.group.id}.name}}/*" | |
| capabilities = ["create", "read", "update", "delete", "list"] | |
| description = "allow all on secrets" | |
| } | |
| rule { |
generic cloud init help and docs
treats user data and cloud init as cloud-init
This is commented out. NOTE: Best if viewed in web browser if currently you are viewing this in Lepton
Based from Brad Traversy's cheatsheet. I just updated it to work for my needs.
| test: | |
| sentinel test -verbose $(shell find . -name "$(name)" -type f ! -path "*/testdata/*") | |
| tests: | |
| sentinel test $(shell find . -name "*.sentinel" -type f ! -path "*/testdata/*") | |
| format: | |
| sentinel fmt -write=true $(shell find . -name "*.sentinel" -type f) | |
| generate: |
Not all Terraform providers are built for arm64.
One solution here is to install Terraform as amd64 which can be easily done from the downloads page.
However, for those who are using and switching between versions of Terraform often, a more streamlined approach is desirable.
Enter asdf.