Releases: cloudposse-archives/terraform-aws-jenkins
Releases · cloudposse-archives/terraform-aws-jenkins
0.3.4
0.3.3
Fix security group ingress rules
what
- Bumped
terraform-aws-elastic-beanstalk-environmentversion - Changed the ingress rule for Jenkins slave Security Group
why
- Latest version of
terraform-aws-elastic-beanstalk-environmentcontrols access to Jenkins master only by provided Security Groups instead of IP ranges - Too broad access to Jenkins slaves from any IP address. It should be controlled by the provided Security Groups as well
0.3.2
0.3.1
0.3.0
0.2.9
what
- Added examples:
- existing_vpc_existing_subnets
- existing_vpc_new_subnets
- new_vpc_new_subnets
- Updated
README
why
- New examples fixed bugs and inconsistencies with the older versions of the modules
- To conform to community standard: https://www.terraform.io/docs/registry/modules/publish.html
0.2.8
what
- Bump
terraform-aws-efs-backupversion to0.3.8
why
- Removed
AllowedValuesfor EC2 instance types interraform-aws-efs-backup - Allowed instance types are optional parameters
- If we use a list of instance type to restrict the values, we'll have to support and update it every time AWS releases new instances
Add option to use IP address as EFS mount point
What
- Add option to use IP address as EFS mount point
Why
- When VPC does not support DNS hostnames we should use IP address for EFS mount target
Add slaves support
what
- Add Security Group for EC2 slaves
- Attach IAM Policy to the Elastic Beanstalk EC2 instance profile
why
- To place Jenkins slaves into a dedicated Security Group and allow the master to connect via SSH
- To allow Jenkins master to launch and control slave EC2 instances
references
Add `README.md`. Add `examples`
What
- Added
README.md - Added
examples
Why
- To conform to community standard: https://www.terraform.io/docs/registry/modules/publish.html