auto changelog action and changelog.md and dependabot.yml file added.

[mamrajyadav]

what
• auto changelog action and changelog.md and dependabot.yml file added.
why
• need to auto changelog action to automatically update the CHANGELOG.YML file
• need to dependabot.yml file to weekly check and automatically create a pull request with the latest tag of modules used in the module

[clouddrove-ci]

Terraform Security Scan Failed

Show Output

Result #1 MEDIUM VPC Flow Logs is not enabled for VPC  
────────────────────────────────────────────────────────────────────────────────
  main.tf:22-43
────────────────────────────────────────────────────────────────────────────────
   22  ┌ resource "aws_vpc" "default" {
   23  │   count = var.vpc_enabled ? 1 : 0
   24  │ 
   25  │   cidr_block                       = var.cidr_block
   26  │   instance_tenancy                 = var.instance_tenancy
   27  │   enable_dns_hostnames             = var.enable_dns_hostnames
   28  │   enable_dns_support               = var.enable_dns_support
   29  │   enable_classiclink               = var.enable_classiclink
   30  └   enable_classiclink_dns_support   = var.enable_classiclink_dns_support
   ..  
────────────────────────────────────────────────────────────────────────────────
          ID aws-ec2-require-vpc-flow-logs-for-all-vpcs
      Impact Without VPC flow logs, you risk not having enough information about network traffic flow to investigate incidents or identify security issues.
  Resolution Enable flow logs for VPC

  More Information
  - https://aquasecurity.github.io/tfsec/latest/checks/aws/ec2/require-vpc-flow-logs-for-all-vpcs/
────────────────────────────────────────────────────────────────────────────────


  timings
  ──────────────────────────────────────────
  disk i/o             84.508µs
  parsing              98.643171ms
  adaptation           93.309µs
  checks               9.964666ms
  total                108.785654ms

  counts
  ──────────────────────────────────────────
  modules downloaded   0
  modules processed    1
  blocks processed     51
  files read           3

  results
  ──────────────────────────────────────────
  passed               2
  ignored              0
  critical             0
  high                 0
  medium               1
  low                  0

  2 passed, 1 potential problem(s) detected.

[clouddrove-ci]

Terraform Security Scan Failed

Show Output

Result #1 MEDIUM VPC Flow Logs is not enabled for VPC  
────────────────────────────────────────────────────────────────────────────────
  main.tf:22-43
────────────────────────────────────────────────────────────────────────────────
   22  ┌ resource "aws_vpc" "default" {
   23  │   count = var.vpc_enabled ? 1 : 0
   24  │ 
   25  │   cidr_block                       = var.cidr_block
   26  │   instance_tenancy                 = var.instance_tenancy
   27  │   enable_dns_hostnames             = var.enable_dns_hostnames
   28  │   enable_dns_support               = var.enable_dns_support
   29  │   enable_classiclink               = var.enable_classiclink
   30  └   enable_classiclink_dns_support   = var.enable_classiclink_dns_support
   ..  
────────────────────────────────────────────────────────────────────────────────
          ID aws-ec2-require-vpc-flow-logs-for-all-vpcs
      Impact Without VPC flow logs, you risk not having enough information about network traffic flow to investigate incidents or identify security issues.
  Resolution Enable flow logs for VPC

  More Information
  - https://aquasecurity.github.io/tfsec/latest/checks/aws/ec2/require-vpc-flow-logs-for-all-vpcs/
────────────────────────────────────────────────────────────────────────────────


  timings
  ──────────────────────────────────────────
  disk i/o             106.901µs
  parsing              86.109133ms
  adaptation           119.101µs
  checks               11.520798ms
  total                97.855933ms

  counts
  ──────────────────────────────────────────
  modules downloaded   0
  modules processed    1
  blocks processed     51
  files read           3

  results
  ──────────────────────────────────────────
  passed               2
  ignored              0
  critical             0
  high                 0
  medium               1
  low                  0

  2 passed, 1 potential problem(s) detected.