-
-
Notifications
You must be signed in to change notification settings - Fork 155
feat: Enable configuration of Docker labels #303
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
feat: Enable configuration of Docker labels #303
Conversation
Allow the user to define a list of Docker labels without providing the entire task definition.
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 📝 WalkthroughWalkthroughAdded Atmos ignore entry to .gitignore. Introduced a new Terraform variable docker_labels and passed it to the container_definition module in main.tf. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
variables.tf (1)
99-104: New variabledocker_labels— LGTM; remember docs.Backward-compatible default and type look right. Please also update README/Inputs table and an example showing label usage.
I can open a docs PR snippet if you want.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
README.mdis excluded by!README.md
📒 Files selected for processing (3)
.gitignore(1 hunks)main.tf(1 hunks)variables.tf(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Summary
🔇 Additional comments (2)
.gitignore (1)
15-17: Add Atmos ignore — LGTM.Good call excluding local Atmos state from the repo.
main.tf (1)
84-84: Verifydocker_labelsinput support in upstream module
Please confirm that the pinned version of the upstream module (cloudposse/ecs-container-definition/awsv0.58.1) declares adocker_labelsvariable of typemap(string)and forwards it to the ECS container definition’sdockerLabelsattribute. If you find that this variable is not present or not wired through:
- Open the module’s
variables.tf(or equivalent) for v0.58.1 and look for a block similar to:variable "docker_labels" { type = map(string) description = "Labels to apply to the container" default = {} }- In the module’s
main.tf, verify thatdocker_labelsis passed into the container definition resource, e.g.:docker_labels = var.docker_labels- If the input is missing or unsupported, bump the module version to the earliest release that adds
docker_labelssupport (check the CHANGELOG or GitHub releases).This will prevent potential “argument not expected” errors when Terraform validates your configuration.
|
/terratest |
|
Posted in Slack as well: An argument named "vpc" is not expected here. |
…ersion AWS provider v6 deprecated `vpc = true` for the EIP resource
|
/terratest |
1. Bucket names now include a timestamp (10 digits) to ensure they're always unique (previously it was a random number between 0 and 999, which increased the risk of a name collision) 2. `rand.Seed` is deprecated, so it was removed. As of Go 1.20, there is no reason to call Seed with a random value
|
/terratest |
|
These changes were released in v2.4.2. |
what
Allow the user to define a list of Docker labels without providing the entire ECS task definition.
why
Some discovery mechanisms rely on
dockerLabels(e.g., "find all containers with labelFOO=bar"). The module already usescloudposse/ecs-container-definition/aws(referenced bycloudposse/ecs-alb-service-task/awslater on to put together a complete ECS task definition) which allows for Docker label configuration, but until now the parameter was not exposed as a variable.references