Comment body too big causing an error - any suggestion ?

hi @peter-evans ,

first of all kudos for this action, it works so nicely !

Secondly, as i was using your action to add a big comment (TF plan output) i’ve bumped into an error like Error: Argument list too long

It it something which can be done to increase the size ?

[tarfeef101]

entertain me: why is posting the comment not in the same workflow as generating the plan? seems like you’re making your life a lot harder by not doing that

hehe @tarfeef102 😉 i did that in first place but the previous/ main job runs on my self-hosted runner (which is EC2 + docker runner) and at that point no matter what value i’ve chosen on the ulimit stack it didn’t cut it. Hence i tried to exclude from the picture the self-runner.

Note i can’t go with running the job on non self-hosted runner because of network layout

my point is:

• runner A actually calls terraform
• the same runner A then takes that plan, slices it up, and uploads to GH This eliminates needing to use env vars, etc. to pass information. It can just put those steps into a script and save the plan in-memory as a variable, and upload it immediately thereafter

[tarfeef101]

If you want to pass an entire plan between steps, consider this fact:

Each step in a job executes on the same runner, allowing the actions in that job to share data with each other.

You can just use files for this.

However, I suggest you just do a little scripting and call a script in a single step rather than use file I/O and multiple steps to do this. Since you’ll need to script handling giant comments anyway, you’re gonna need complex steps no matter what.