Post Workflow Hooks

Post workflow hooks can be defined to run scripts after default or custom workflows are executed. Post workflow hooks differ from custom workflows in that they are run outside of Atlantis commands. Which means they do not surface their output back to the PR as a comment.


Post workflow hooks can only be specified in the Server-Side Repo Config under the repos key.

Atlantis Command Targetting

By default, the workflow hook will run when any command is processed by Atlantis. This can be modified by specifying the commands key in the workflow hook containing a comma delimited list of Atlantis commands that the hook should be run for. Detail of the Atlantis commands can be found in Using Atlantis.


    - id: /.*/
        - run: ./
          description: Plan Hook
          commands: plan
        - run: ./
          description: Plan & Apply Hook
          commands: plan, apply

Use Cases

Cost estimation reporting

You can add a post workflow hook to perform custom reporting after all workflows have finished.

In this example we use a custom workflow to generate cost estimates for each workflow using Infracostopen in new window, then create a summary report after all workflows have completed.

# repos.yaml
      - init
      - plan
      - run: infracost breakdown --path=$PLANFILE --format=json --out-file=/tmp/$BASE_REPO_OWNER-$BASE_REPO_NAME-$PULL_NUM-$WORKSPACE-$REPO_REL_DIR-infracost.json
  - id: /.*/
    workflow: myworkflow
      - run: infracost output --path=/tmp/$BASE_REPO_OWNER-$BASE_REPO_NAME-$PULL_NUM-*-infracost.json --format=github-comment --out-file=/tmp/
        description: Running infracost
      # Now report the output as desired, e.g. post to GitHub as a comment.
      # ...

Customizing the Shell

By default, the commands will be run using the 'sh' shell with an argument of '-c'. This can be customized using the shell and shellArgs keys.


    - id: /.*/
        - run: |
            echo 'atlantis.yaml config:'
            cat atlantis.yaml
          description: atlantis.yaml report
          shell: bash
          shellArgs: -cv


Custom run Command

This is very similar to custom workflow run command.

- run: custom-command
runstringnonenoRun a custom command
descriptionstringnonenoPost hook description
shellstring'sh'noThe shell to use for running the command
shellArgsstring'-c'noThe shell arguments to use for running the command


  • run commands are executed with the following environment variables:
    • BASE_REPO_NAME - Name of the repository that the pull request will be merged into, ex. atlantis.
    • BASE_REPO_OWNER - Owner of the repository that the pull request will be merged into, ex. runatlantis.
    • HEAD_REPO_NAME - Name of the repository that is getting merged into the base repository, ex. atlantis.
    • HEAD_REPO_OWNER - Owner of the repository that is getting merged into the base repository, ex. acme-corp.
    • HEAD_BRANCH_NAME - Name of the head branch of the pull request (the branch that is getting merged into the base)
    • HEAD_COMMIT - The sha256 that points to the head of the branch that is being pull requested into the base. If the pull request is from Bitbucket Cloud the string will only be 12 characters long because Bitbucket Cloud truncates its commit IDs.
    • BASE_BRANCH_NAME - Name of the base branch of the pull request (the branch that the pull request is getting merged into)
    • PULL_NUM - Pull request number or ID, ex. 2.
    • PULL_URL - Pull request URL, ex.
    • PULL_AUTHOR - Username of the pull request author, ex. acme-user.
    • DIR - The absolute path to the root of the cloned repository.
    • USER_NAME - Username of the VCS user running command, ex. acme-user. During an autoplan, the user will be the Atlantis API user, ex. atlantis.
    • COMMENT_ARGS - Any additional flags passed in the comment on the pull request. Flags are separated by commas and every character is escaped, ex. atlantis plan -- arg1 arg2 will result in COMMENT_ARGS=\a\r\g\1,\a\r\g\2.
    • COMMAND_NAME - The name of the command that is being executed, i.e. plan, apply etc.
    • OUTPUT_STATUS_FILE - An output file to customize the success or failure status. ex. echo 'failure' > $OUTPUT_STATUS_FILE.
Last Updated:
Contributors: Simon Heather, Adam Verigin, Fabiano Soares Honorato, Giovanni Tirloni, Koen van Zuijlen, Rui Chen, Shouichi Kamiya, Tim McFadden, ilamtap