Skip to main content

terraform iterate over string

By
ingress = "22:192.168.0.0/24:tcp,80:172.16.120.0/16:tcp,8080:0.0.0.0/0:tcp"
egress = "22:192.168.0.0/24:tcp,80:172.16.120.0/16:tcp,8081:127.0.0.0/0:udp"

resource "openstack_compute_secgroup_v2" "secgroup_1" {
name = "secgroup"
description = "my security group"

count = "${length(split(",",var.ingress))}"
rule {
from_port = "${element(split(":",element(split(",",var.ingress),count.index)), 0)}"
to_port = "${element(split(":",element(split(",",var.ingress),count.index)), 0)}"
ip_protocol = "${element(split(":",element(split(",",var.ingress),count.index)), 2)}"
cidr = "${element(split(":",element(split(",",var.ingress),count.index)), 1)}"
}
}

Note: This will create multiple security groups if you want single security group and multiple rules use following code:

resource "openstack_networking_secgroup_v2" "secgroup" {
name = "secgroup"
description = "My neutron security group"
}

 

resource "openstack_networking_secgroup_rule_v2" "secgroup_rule_ingress" {

count = "${length(split(",",var.ingress))}"
direction = "ingress"
ethertype = "IPv4"
protocol = "${element(split(":",element(split(",",var.ingress),count.index)), 2)}"
port_range_min = "${element(split(":",element(split(",",var.ingress),count.index)), 0)}"
port_range_max = "${element(split(":",element(split(",",var.ingress),count.index)), 0)}"
remote_ip_prefix = "${element(split(":",element(split(",",var.ingress),count.index)), 1)}"
security_group_id = "${openstack_networking_secgroup_v2.secgroup_1.id}"
}

resource "openstack_networking_secgroup_rule_v2" "secgroup_rule_egress" {

count = "${length(split(",",var.egress))}"
direction = "egress"
ethertype = "IPv4"
protocol = "${element(split(":",element(split(",",var.egress),count.index)), 2)}"
port_range_min = "${element(split(":",element(split(",",var.egress),count.index)), 0)}"
port_range_max = "${element(split(":",element(split(",",var.egress),count.index)), 0)}"
remote_ip_prefix = "${element(split(":",element(split(",",var.egress),count.index)), 1)}"
security_group_id = "${openstack_networking_secgroup_v2.secgroup_1.id}"
}

 
Labels:

Comments

Post a Comment

Popular posts from this blog

Terraform

By
Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. Configuration files describe to Terraform the components needed to run a single application or your entire datacenter. Terraform generates an execution plan describing what it will do to reach the desired state, and then executes it to build the described infrastructure. As the configuration changes, Terraform is able to determine what changed and create incremental execution plans which can be applied. The infrastructure Terraform can manage includes low-level components such as compute instances, storage, and networking, as well as high-level components such as DNS entries, SaaS features, etc. The key features of Terraform are: Infrastructure as Code : Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and...
16 comments
Read more

Salt stack issues

By
The function “state.apply” is running as PID Restart salt-minion with command:  service salt-minion restart No matching sls found for ‘init’ in env ‘base’ Add top.sls file in the directory where your main sls file is present. Create the file as follows: 1 2 3 base: 'web*' : - apache If the sls is present in a subdirectory elasticsearch/init.sls then write the top.sls as: 1 2 3 base: '*' : - elasticsearch.init How to execute saltstack-formulas create file  /srv/pillar/top.sls  with content: base : ' * ' : - salt create file  /srv/pillar/salt.sls  with content: salt : master : worker_threads : 2 fileserver_backend : - roots - git gitfs_remotes : - git://github.com/saltstack-formulas/epel-formula.git - git://github.com/saltstack-formulas/git-formula.git - git://github.com/saltstack-formulas/nano-formula.git - git://github.com/saltstack-f...
12 comments
Read more

Helm: Installation and Configuration

By
PREREQUISITES You must have Kubernetes installed. We recommend version 1.4.1 or later. You should also have a local configured copy of  kubectl . Helm will figure out where to install Tiller by reading your Kubernetes configuration file (usually  $HOME/.kube/config ). This is the same file that  kubectl  uses. To find out which cluster Tiller would install to, you can run  kubectl config current-context or  kubectl cluster-info . $ kubectl config current-context my-cluster INSTALL HELM Download a binary release of the Helm client. You can use tools like  homebrew , or look at  the official releases page . For more details, or for other options, see  the installation guide . INITIALIZE HELM AND INSTALL TILLER Once you have Helm ready, you can initialize the local CLI and also install Tiller into your Kubernetes cluster in one step: $ helm init This will install Tiller into the Kubernetes cluster you saw with  kubectl config current-context . TIP:  Want to install into a different cl...
4 comments
Read more