0.3.0

What’s Changed

include new pipelines @brunodasilvalenga (#8)

Include new features o github actions.

0.2.0

What’s Changed

🚀 Enhancements

Feature/checkov @alexandrealvao (#7)

Integrate Checkov with the pipeline.

Types of changes

What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

0.1.0

What’s Changed

Implement auto releases @mcosta1105 (#5)

Add auto release workflows

🐛 FIX: Terraform docs CI @caiovfernandes (#3)

This pull request fixes the terraform docs automation, modifying the file docs.yml to run on any pull request.

📦 NEW: Add CONTRIBUTING.md @caiovfernandes (#2)

Add the contributing code to public repos.

Add project guidelines and issue/prs templates @caiovfernandes (#1)

This pull request push project guidelines and templates files to improve repository community health.