This message was deleted.
# atlantis-community
s
This message was deleted.
a
Copy code
repos:
  - id: <http://internal-bitbucket.com/Project/repo|internal-bitbucket.com/Project/repo>
    branch: /TEST-20037/
    plan_requirements: [mergeable]
    apply_requirements: [approved, mergeable]
    import_requirements: [approved, mergeable]
    pre_workflow_hooks:
      - run: terragrunt-atlantis-config generate --output atlantis.yaml --autoplan --parallel --create-workspace
    workflow: terragrunt
workflows:
  terragrunt:
    plan:
      steps:
        - env:
            name: TERRAGRUNT_TFPATH
            command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
        - run: terragrunt plan -input=false -out=$PLANFILE
        - run: terragrunt show -json $PLANFILE > $SHOWFILE
the only flags being used to start the server are bitbucket params, repo-allowlist, and repo-config
also, is there a way for atlantis to automatically clean up old plans? that would also be pretty helpful and reduce the noise
d
Hey Abe, thanks for reaching out. There is a way to hide old plan comments but it only supported by the GitHub backend atm. https://www.runatlantis.io/docs/server-configuration.html#hide-prev-plan-comments As for the output stripping, yes it should be working. I would encourage you to file an issue so we and the community can dig into it further.
a
thanks, dylan. i have requested access to our internal enterprise github and will be integrating with it today for comparison. i suspect we will want to move forward with github once people can see the difference between the two experiences
d
Yeah unfortunately, as much as we try to support many VCS backends, the more popular ones (GitHub for example) tend to be a better experience just from usage and reports
a
team agrees the overall experience with github is way better than bitbucket. just having the output folded up and not immediately showing hundreds of lines of output is much better. we're still seeing the "Initializing the backend.." and "Refreshing state..." in the output though in github enterprise i'll open a ticket per your suggestion above
d
Thank you, we'll dig into it once you do
a
l
FWIW we do remove all of this output if you're doing the built-in plan step, it's because you're using the custom step.
a
ah ok, it's because we're using terragrunt then. that makes sense. is whatever we write to the $SHOWFILE what is added to the PR comment or is there more to it?