Atlantis: Bitbucket server comments too long

[lkysow]

Bitbucket has a max of 32k chars. Will need to split the output into multiple comments like with GitHub.

Via @BlackTurtle123

[BlackTurtle123]

Or purge all the "refresh" data would also work I think?
Since the actual changes matter most

[lkysow]

Yes @majormoses also suggested that. I'll look into it.

[jonboulle]

Having atlantis purge the refresh data would be great and allow me to remove my poor man's atlantis.yaml workaround:

      - run: terraform plan -refresh -no-color -out $PLANFILE -var-file ./dev.tfvars | fgrep -v \"Refreshing state...\"

[BlackTurtle123]

Having atlantis purge the refresh data would be great and allow me to remove my poor man's atlantis.yaml workaround:

      - run: terraform plan -refresh -no-color -out $PLANFILE -var-file ./dev.tfvars | fgrep -v \"Refreshing state...\"

I might for now use the poor man's workaround since I am currently doing only a PoC. But yes a "clean" way might be very good

[majormoses]

@BlackTurtle123 if you upgrade to 0.4.11 it will do it for you now I verified it works on my systems.

[kipkoan]

I just ran into this same problem. I'll look into fixing this during our next sprint, as we are doing some major refactoring across a lot of repos, which results in some large terraform plans.

$ terraform plan | wc
    338    1449   39121

$ atlantis version
atlantis 0.4.11

(actually running commit https://github.com/runatlantis/atlantis/commit/deebb22b5d04abb63862c0bbdf0841ff1ccdf300)

Atlantis error:

2018/11/16 22:48:03 command_runner.go:257: [ERROR] Analytics Terraform/zoml-platform#8: 
Unable to comment: making request "POST .../rest/api/1.0/projects/anatf/repos/zoml-platform/pull-requests/8/comments" 
unexpected status code: 400, body: {"errors":[{"context":"text","message":
"Please enter a non-empty value less than 32768 characters","exceptionName":null}]}

[lkysow]

We can take the code from github_client and split the comment into multiple comments. We just need to use a different separator because we don't use the <details> format for Bitbucket.