11/28/2022, 8:46 AM
Hey everyone! Been using Pulumi in production for a few months now and it works great! What's the most reliable and robust way to determine which resources were updated via the Pulumi GitHub action?
We recently ran into an issue with Pulumi's GitHub action output being too long. Our GitHub workflows need to conditionally perform certain jobs based on which resources were updated. At the moment we're: • Saving the entire output log into an env variable (which seems really bad) • Writing this env variable into a file • Using this file as input for a bash command that determines whether to run a particular job or not. The most recent runs have been causing the GitHub actions to fail because the "argument list is too long". I'm assuming that this is caused by the output being too long (docker build log)
Any help is really appreciated!


11/28/2022, 12:40 PM
That is a very good question and interesting use case. Maybe @limited-rainbow-51650 has some input/idea