Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update terraform cloudposse/sns-lambda-notify-slack/aws to v0.9.0 #46

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 11, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
cloudposse/sns-lambda-notify-slack/aws (source) module minor 0.7.0 -> 0.9.0

Release Notes

cloudposse/terraform-aws-sns-lambda-notify-slack (cloudposse/sns-lambda-notify-slack/aws)

v0.9.0

Compare Source

v0.8.0

Compare Source

fix: add an attribute to examples/completed to avoid name conflict in test concurrent runs @​gberenice (#​60)

what

  • Adds an attribute to the examples/competed root module - the MD5 hash of a timestamp. Thit adds a "random" attribute to the resources and helps to avoid resource name conflict during the concurrent runs, [e.g.]:
    Error: creating CloudWatch Logs Log Group (/aws/lambda/eg-test-sns-default): operation error CloudWatch Logs:
    CreateLogGroup, https response error StatusCode: 400, RequestID: 1eefd044-082e-4b8e-8c3b-0b3c3f2dd8a8,
    ResourceAlreadyExistsException: The specified log group already exists
  • Bumps terraform-aws-modules/notify-slack/aws to support newer Python version before 3.8 EOL

why

v0.7.2

Compare Source

Add tags @​rtest12 (#​59)

what

  • Use tags = module.this.tags on the notify_slack resource.

why

  • Enhanced manageability: Tags enable better resource management, cost tracking, and security strategies.
  • Consistency: Tagging the notify_slack resource provides consistency across all project resources.
  • Discovery: Tags assist in faster resource locating when filtering or searching.

🤖 Automatic Updates

Update GitHub Workflows to use shared workflows from '.github' repo @​osterman (#​58)

what

  • Update workflows (.github/workflows) to use shared workflows from .github repo

why

  • Reduce nested levels of reusable workflows
Update GitHub Workflows to Fix ReviewDog TFLint Action @​osterman (#​56)

what

  • Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

  • The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @​osterman (#​55)

what

  • Update workflows (.github/workflows/settings.yaml)

why

  • Support new readme generation workflow.
  • Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​54)

what

  • Install latest GitHub Action Workflows

why

  • Use shared workflows from cldouposse/.github repository
  • Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @​osterman (#​51)

what

  • Install a repository config (.github/settings.yaml)

why

  • Programmatically manage GitHub repo settings
Update Scaffolding @​osterman (#​49)

what

  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify

why

  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel

v0.7.1

Compare Source

🚀 Enhancements

Added variable lambda_source_path to support custom lambda @​vladsmrt (#​46)

what

why

references

🤖 Automatic Updates

Update Terraform terraform-aws-modules/notify-slack/aws to 5.6 @​renovate (#​48)

This PR contains the following updates:

Package Type Update Change
terraform-aws-modules/notify-slack/aws (source) module minor 5.5 -> 5.6

Release Notes
terraform-aws-modules/terraform-aws-notify-slack (terraform-aws-modules/notify-slack/aws)
v5.6.0

Compare Source

Features


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner June 11, 2024 10:04
@renovate renovate bot added the auto-update This PR was automatically generated label Jun 11, 2024
@renovate renovate bot requested review from a team as code owners June 11, 2024 10:04
@renovate renovate bot requested review from johncblandii and gberenice June 11, 2024 10:04
Copy link

mergify bot commented Jun 11, 2024

/terratest

@renovate renovate bot force-pushed the renovate/cloudposse-sns-lambda-notify-slack-aws-0.x branch from f05b377 to 0f76847 Compare July 11, 2024 12:42
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/sns-lambda-notify-slack/aws to v0.7.2 chore(deps): update terraform cloudposse/sns-lambda-notify-slack/aws to v0.8.0 Jul 11, 2024
@gberenice
Copy link

/terratest

@renovate renovate bot force-pushed the renovate/cloudposse-sns-lambda-notify-slack-aws-0.x branch from 0f76847 to 7dd262e Compare July 11, 2024 18:19
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/sns-lambda-notify-slack/aws to v0.8.0 chore(deps): update terraform cloudposse/sns-lambda-notify-slack/aws to v0.9.0 Jul 11, 2024
@gberenice
Copy link

/terratest

@gberenice gberenice merged commit ef73e4e into main Jul 11, 2024
14 checks passed
@gberenice gberenice deleted the renovate/cloudposse-sns-lambda-notify-slack-aws-0.x branch July 11, 2024 19:03
Copy link

These changes were released in v0.5.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-update This PR was automatically generated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant