powerful-art-87860
07/19/2022, 7:59 AMpropagateTags
property from the aws.ecs.Service:
1. setting it's value for the first time triggers a Service create-replacement.
2. changing it afterwards also triggers a Service create-replacement.
The pulumi up detail shows the name
, id
and propagateTags
changing. The name
and id
change is due to the ending randomId from pulumi changing.
Tried TASK_DEFINITION, SERVICE, NONE and removing the property, it always requires a replacement.
I understand that changing the name triggers a replacement but why does propagateTags
change the ending randomId from name
?
Has anyone had this issue?worried-rain-74420
07/19/2022, 1:09 PMpropagateTags
field. I noticed it doesn’t have the “replace-on-change” icon (see screenshot). So changing the propagateTags
field by itself shouldn’t cause a replacement (if it does, something’s buggy).
But I think the actual issue is a little different. Can you try setting the name
field to a string literal?
I suspect you’re not setting the name
field yourself each time, so Pulumi generates a random name. Since that random name is different from the randomly generated name from the prior run, the engine detects a difference between the old and the new name, on a property that requires a replaceOnChange
(the name property). That’s why you’ll recreate the Service each time.
That’s my guess at the cause of your issue. I’m pretty new to Pulumi myself, so I apologize if I’m directing you down the wrong path! But you might want to give that a go 😄powerful-art-87860
07/19/2022, 2:26 PMreplace-on-change
icon and I agree that changing other properties that don't have it does not trigger a create-replacement.
Changing propagateTags
by itself though triggers a replacement (and as you said, it doesn't have the icon).
Is this a known bug then?
If this is something we must accept (due to inner pulumi workings), could a replace-on-change
icon be added here as well?worried-rain-74420
07/19/2022, 2:35 PMname
field being unset as I mentioned above. Have you tried providing a string literal to set the name
of the ECS Service? Or could you provide a redacted code snippet?
If it’s true that the error is actually with propagateTags
, then yes, that would most likely be a bug for a missing icon.
Pulumi doesn’t determine which properties are replace-on-change
and which aren’t. I believe that’s determined by AWS, and part of their public API. I’m still more keen on the name
theory myself 🙂little-cartoon-10569
07/19/2022, 10:13 PMpowerful-art-87860
08/03/2022, 10:54 AMlittle-cartoon-10569
08/03/2022, 8:06 PMpowerful-art-87860
08/04/2022, 6:03 AMbreezy-butcher-78604
08/11/2022, 8:08 AM