v0.14.0

Ingress sg port fix @heathsnow (#31)

what

• fix ingress security groups
• if this module creates the security group then output the security_group_id

why

• Having protocol set to "tcp" will set the to/from ports
  to the "0" specified. Port 0 is not an ActiveMQ or
  RabbitMQ broker port. Instead, use port 65535 for the to_port
  to allow all TCP traffic.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule
• closed #29
• closes #30

v0.13.0

Dynamic logs block @heathsnow (#28)

what

• RabbitMQ support via dynamic logs block
  • RabbitMQ general logs cannot be enabled.
    • hashicorp/terraform-provider-aws#18067

why

• Support engine_type = "RabbitMQ"

references

• hashicorp/terraform-provider-aws#18067

• Closes #24 insofar as the provider doesn't currently support enabling general logging at this time.
• I think #18 can also be closed.

v0.12.0

add `tags` argument to aws_ssm_parameter resources @heathsnow (#27)

what

• Add tags argument to aws_ssm_parameter resources.

why

• Testing Terraform code often involves adhering to compliance standards. In this case I have a compliance requirement to include certain tags on all resources that accept the tags argument.

references

• https://terraform-compliance.com/pages/Examples/tags_related.html
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ssm_parameter#tags

v0.11.0

Add support for tags @gberenice (#26)

what

• Add support for tags

why

• This feature is available in aws_mq_broker, but not enabled in module

references

• NA

v0.10.1

🚀 Enhancements

create random username and password for admin user only if needed @treksler (#25)

what

• only create random strings for admin user and admin password, if we are actually going to use them
• the logic is that only if the module is enabled, and the admin user is enabled and if the admin user was not passed in (i.e. is unset) only then do we need to create these random strings

why

• the admin user is a dynamic property and it does NOT get created, if admin user is not enabled
• we do not need to create these random strings when the dynamic block does not created
• since the admin user is a dynamic block, we do NOT need to worry about username and password being required fields
• They are not required because the whole block won't exist

references

• follow up for 867068d

v0.10.0

create admin secrets only when admin user is created @gberenice (#23)

what

• create resources related to admin user only when this user is enabled (based on engine type)
• minor improvements for locals usage

why

• no need to create extra resources

references

• NA

v0.9.0

only create admin user for activemq @treksler (#22)

what

• only create admin user for activemq

why

• Rabbitmq does not support admin user with console access and groups at this time

references

• closes #21

v0.8.0

Implement enabled toggle in main and outputs @treksler (#20)

what

• Implement module enabled toggle in main and outputs files

why

• module enabled functionality is documented, and implemented for security groups
• users will expect to be able to disable all resources with enabled flag

references

• Use closes #19

v0.7.0

Update CODEOWNERS @maximmi (#16)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.6.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#17)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.