-
-
Notifications
You must be signed in to change notification settings - Fork 0
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/label/null to v0.25.0 #3
base: main
Are you sure you want to change the base?
Conversation
/terratest |
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟠 Require terratestWaiting checks:
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
This PR contains the following updates:
0.24.1
->0.25.0
Release Notes
cloudposse/terraform-null-label (cloudposse/label/null)
v0.25.0
Compare Source
Add "tenant", "labels_as_tags", and "descriptors" @Nuru (#132)
what
id
component:tenant
labels_as_tags
controls which labels are exported as tagsdescriptor_formats
generates new outputdescriptors
terraform-terraform-label
why
null-label
tenant
,labels_as_tags
,descriptor_formats
, add additional clarification, stop promoting obsolete moduleFix: Update README Snippets @korenyoni (#130)
what
why
references
Bridgecrew compliance @Nuru (#125)
what
.gitignore
why
note
The PR can and should be merged into
master
to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging tomaster
will update the README and badges, so is worthwhile, and the changes will move forward into the next release.Properly output descriptors of chained modules @Nuru (#133)
what
why
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.