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

ECS Container definition permanent diff in Environment #4336

Closed
stefan01 opened this issue Jul 30, 2024 · 4 comments
Closed

ECS Container definition permanent diff in Environment #4336

stefan01 opened this issue Jul 30, 2024 · 4 comments
Assignees
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec needs-repro Needs repro steps before it can be triaged or fixed resolution/no-repro This issue wasn't able to be reproduced

Comments

@stefan01
Copy link

Describe what happened

Reopen of #1738 (comment)

I am still experiencing this issue even with the newest version 6.47.0 :(
More specifically, it is effecting the ordering of the Environment section and it always wants to remove the Properties:

MountPoints : []
SystemControls : []
VolumesFrom : []

Sample program

json.dumps(
                [
                    {
                        "Name": "task-name",
                        "Essential": True,
                        "Image": ....,
                        "Cpu": cpu,
                        "MemoryReservation": memory,
                        "LogConfiguration": {
                            "LogDriver": "awslogs",
                            "Options": {
                                "awslogs-region": "region",
                                "awslogs-group": "log_group",
                                "awslogs-stream-prefix": "prefix",
                            },
                        },
                        "Environment": [
                            {
                                "Name": "Z",
                                "Value": "Z",
                            },
                            {
                                "Name": "A",
                                "Value": "A",
                            },
                            {
                                "Name": "B",
                                "Value": "B",
                            },
                            {
                                "Name": "C",
                                "Value": "C",
                            },
                        ],
                    },
                ],
            ),

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

CLI
Version 3.125.0
Go Version go1.22.5
Go Compiler gc

Host
OS ubuntu
Version 22.04
Arch x86_64

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).

@stefan01 stefan01 added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Jul 30, 2024
@corymhall
Copy link
Contributor

@stefan01 can you provide us a full example that we can use to reproduce the issue? Thanks!

@corymhall corymhall added needs-repro Needs repro steps before it can be triaged or fixed awaiting-feedback Blocked on input from the author and removed needs-triage Needs attention from the triage team labels Jul 30, 2024
@yenoromm
Copy link

yenoromm commented Aug 6, 2024

@stefan01 I am seeing this too, seems all keys in the container definition json are stored in state as capitalized now too also causing a diff "Cpu" > "cpu". Values that were previously undefined like HealthCheck.Interval, SystemControls etc are stored in state even when not defined.

@t0yv0
Copy link
Member

t0yv0 commented Aug 13, 2024

Sorry this is still affecting your use of Pulumi. Do you have a complete repro, a complete Pulumi program that demonstrates the behavior? That would really help us solve this quickly.

@mikhailshilkov
Copy link
Member

Another reminder to provide us with a repro program - otherwise we'll have to close the issue as non-actionable. Thank you!

@t0yv0 t0yv0 added the resolution/no-repro This issue wasn't able to be reproduced label Sep 27, 2024
@t0yv0 t0yv0 closed this as completed Sep 27, 2024
@t0yv0 t0yv0 self-assigned this Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec needs-repro Needs repro steps before it can be triaged or fixed resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

5 participants