-
Notifications
You must be signed in to change notification settings - Fork 160
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
EventBridge replaces default CPU/Memory on Override to ECS #5253
Labels
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
kind/bug
Some behavior is incorrect or out of spec
Comments
Hey @quinnjr, thanks for reporting and sorry you've hit this. Can you please provide a self-contained program which reproduces the issue? That'd help us a lot in narrowing down the cause. The code excerpts look like they might be part of a component. |
|
@quinnjr thanks for the repro. It looks like this is a bug with the upstream provider. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
kind/bug
Some behavior is incorrect or out of spec
Describe what happened
EventBridge invocations of ECS tasks are overriding the CPU/Memory configurations of the container being invoke on ECS with defaults of 0 CPU and 0 Memory unless specifically non-defaulted in the EventBridge configuration.
Sample program
EventBridge pipe:
ECS Task Definition:
Log output
No log output is given, but the override on the container definition in the EventBridge pipe shows 0 on CPU/Memory if defaults are not set.
Affected Resource(s)
No response
Output of
pulumi about
CLI
Version 3.153.0
Go Version go1.23.6
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.66.2
resource awsx 2.19.0
resource docker 4.5.8
resource docker 3.6.1
resource grafana 0.4.2
language nodejs 3.153.0
resource random 4.16.8
Host
OS ubuntu
Version 22.04
Arch x86_64
This project is written in nodejs: executable='/home/joseph/.local/share/nvm/versions/node/v22.13.1/bin/node' version='v22.13.1'
Backend
Name pulumi.com
URL https://app.pulumi.com/jquinn
User jquinn
Organizations jquinn, recordboss
Token type personal
Dependencies:
NAME VERSION
ts-node 10.9.2
uuid 9.0.1
@pulumi/aws 6.66.2
@typescript-eslint/eslint-plugin 8.19.1
@typescript-eslint/parser 8.19.1
eslint-plugin-unicorn 55.0.0
husky 9.1.7
typescript 5.7.2
@pulumi/awsx 2.19.0
@types/node 20.17.12
eslint-config-prettier 9.1.0
eslint-plugin-prettier 5.2.1
eslint 9.17.0
@aws-sdk/client-rds-data 3.723.0
@pulumi/pulumi 3.145.0
@types/aws-sdk 2.7.4
lint-staged 15.3.0
@pulumi/random 4.16.8
@pulumiverse/grafana v0.4.2
aws-sdk 2.1692.0
prettier 3.4.2
Pulumi locates its logs in /tmp by default
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: