-
Notifications
You must be signed in to change notification settings - Fork 155
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
TaskDefinition Always Replace When Default Values Not Included in ContainerDefinitions #1985
Comments
Do you mind sharing a code snippet of how you're creating the task definition? |
After a bit more investigation I've narrowed it down to just the
|
Same problem in |
So, I see the container outputs different ENV, which doesn't merge with the user environments.
|
As I understand, |
@mattsleiman-discovery for Fargate task definition I was able to fix this by providing default health check values, for the rest like CPU and memory I didn't mention it as for Fargate its not mandatory and it does not replace container definition anyway, the only values for me that kept replacing containerdefinitions was heathCheck values:
|
This is effectively due to hashicorp/terraform-provider-aws#11526 in upstream. The normalization used in the diff implementation could in principle handle all of the topics raised here:
|
I have an ECS service that is having it's task definition replaced every time I run
pulumi up
even if no changes are made to the task definition. The diff that pulumi is reporting shows the only change being the container definitions string. It appears that the container definitions string in the stack's state has default values for several fields filled in (e.g. cpu=0, mountPoints=[], volumesFrom=[], etc.) while my code does not. The comparison isn't adding those default values before comparing the two strings so it reports they are different. I've manually added all the default values and nowpulumi up
correctly reports there are no changes. Is it possible to have those default values considered when doing the comparison so I don't have to make sure they are always present in my code? I'm using version 1.14.1 with the golang SDK.The text was updated successfully, but these errors were encountered: