Store plan output in external source such as S3 and post link in the PR comment instead of full output

[colinjfw]

It would be great to have an option in atlantis to store the plan output on the atlantis server. The github comment could link to a page with just the plain text view of the output. Benefits to this:

• This could fix the issue in Formatting is broken when comments are continued on GitHub #111 with long plan output.
• If secrets were exposed in a plan it would only be those who had access to the atlantis server that could see them.

The github comment could link to the atlantis server where the output would be stored.

[colinjfw]

I would be willing to take this on, looking at the code so far I think I could handle this!

[lkysow]

Sorry for the delay responding! I think this is a good idea because in the future I want Atlantis to have its own UI for viewing plans and their states and so eventually we'll link to that UI.

[colinjfw]

@lkysow I won't be able to take this on for another few weeks. Definitely interested in taking it on though, I will keep this up to date but if someone else grab's this ticket no worries from me.

[bewie]

Hi,
Do you know if this ticket is still relevant; because since I use vault provider with terraform, I have lot of issues with sensitive data in output. And terrahelp cannot catch it.
I think the only stable solution should be to store the output on Atlantis server (or S3).

[lkysow]

Yes I think this ticket is still relevant, especially for your use case.

[JoshiiSinfield]

Hi,
I have a similar use case. I'd like the ability to store plan outputs in S3 or DynamoDB.

We run Atlantis in Fargate, and leave it on 24/7 but we'd like to fire it up only when we receive a request to the webhook (could be done by scaling or by a lambda target on ALB).

But in order to make this feasible/match the current functionality we'd need to store the plan output NOT on the atlantis server.

@lkysow Would you like a different issue raising for S3/DynamoDB? keep this one as storing on server?

Cheers,
Josh

[lkysow]

@JoshiiSinfield this has already been discussed in #265 which was closed as won't do. See my comment: #265 (comment)

[JoshiiSinfield]

@lkysow sorry, my brief search failed me!

I'd be willing to put some time in if you'd be able to direct me where to start/with a plan of action, because as you know I'm still learning go!

It would certainly be a cost saver for us. Along with a great opportunity to contribute for myself!

[natalysheinin]

+1 for running atlantis serverless with the option for remote plans to be in GCS (and/or S3).

[christopher-dG]

Bump: when huge plans get split across 10 comments, I would love to be able to click a link to see the full, coloured output.

[jhebert-coursera]

I guess I'll add another comment in support of this request, although in our case I think S3 would be ideal. We have many configured Atlantis projects, some of which are quite large, and a module change that impacts numerous projects is very difficult to read as Github comments. In the extreme case, we might have 25 projects being planned concurrently, each with thousands of lines of output, requiring a pretty tedious amount of scrolling and clicking "Show Output" as Github collapses things.

That being said, Atlantis has been a game-changer for us, so thanks for all of the work on this!

[nitrocode]

Related issue #936

Technically we do have a way of seeing the plan stored on the server via websockets using the plan/apply "Details" link at the bottom of a Github PR. The plan unfortunately is still ephemeral. If you restart atlantis, you can no longer see the plan outputs.

It would be great to store the plan in S3 or some external store instead. PRs are always welcome.

[jamengual]

there might be enough information here #2157