Adding an Output to a stack does not count as a change so the stack is not deployed

[rix0rrr]

Reproduction

Have a stack, deploy it. Add an Output object to it. Deploy it again.

Expectation

Stack is deployed and the Output is added.

Reality

 ⏳  Starting deployment of stack XXXX...
 ✅  Stack was already up-to-date, it has ARN XXXXXX

[RomainMuller]

Isn't this CloudFormation behavior?

[rix0rrr]

Might be, but it's still surprising behavior from the user's PoV.

[RomainMuller]

I am not denying that. Just wanted to make sure.

[coderbyheart]

No, if you add an output and deploy it using cloud formation (CLI or Web UI) the output is added.

[rix0rrr]

You are right, what Romain was referring to I think is the ChangeSet that is created in the process showing "no changes" (at least at the resource level). We're interpreting that response as "nothing to do", and hence doing nothing.

[ijcd]

I'm hitting this as well. Is there a workaround?

[eladb]

@ijcd make some other change to the template such as adding metadata.

[eladb]

@rix0rrr this is resolved, correct?

[rix0rrr]

Yes, was fixed in #2029