forked from cloudposse/terraform-aws-eks-cluster
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updates for TF 0.14, pin Kubernetes provider (cloudposse#94)
- Loading branch information
Showing
12 changed files
with
130 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,7 +27,7 @@ jobs: | |
| make init | ||
| make github/init/context.tf | ||
| make readme/build | ||
| echo "::set-output name=create_pull_request=true" | ||
| echo "::set-output name=create_pull_request::true" | ||
| fi | ||
| else | ||
| echo "This module has not yet been updated to support the context.tf pattern! Please update in order to support automatic updates." | ||
|
|
@@ -38,6 +38,8 @@ jobs: | |
| uses: cloudposse/actions/github/[email protected] | ||
| with: | ||
| token: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }} | ||
| committer: 'cloudpossebot <[email protected]>' | ||
| author: 'cloudpossebot <[email protected]>' | ||
| commit-message: Update context.tf from origin source | ||
| title: Update context.tf | ||
| body: |- | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,86 @@ | ||
| name: Auto Format | ||
| on: | ||
| pull_request_target: | ||
| types: [opened, synchronize] | ||
|
|
||
| jobs: | ||
| auto-format: | ||
| runs-on: ubuntu-latest | ||
| container: cloudposse/build-harness:slim-latest | ||
| steps: | ||
| # Checkout the pull request branch | ||
| # "An action in a workflow run can’t trigger a new workflow run. For example, if an action pushes code using | ||
| # the repository’s GITHUB_TOKEN, a new workflow will not run even when the repository contains | ||
| # a workflow configured to run when push events occur." | ||
| # However, using a personal access token will cause events to be triggered. | ||
| # We need that to ensure a status gets posted after the auto-format commit. | ||
| # We also want to trigger tests if the auto-format made no changes. | ||
| - uses: actions/checkout@v2 | ||
| if: github.event.pull_request.state == 'open' | ||
| name: Privileged Checkout | ||
| with: | ||
| token: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }} | ||
| repository: ${{ github.event.pull_request.head.repo.full_name }} | ||
| # Check out the PR commit, not the merge commit | ||
| # Use `ref` instead of `sha` to enable pushing back to `ref` | ||
| ref: ${{ github.event.pull_request.head.ref }} | ||
|
|
||
| # Do all the formatting stuff | ||
| - name: Auto Format | ||
| if: github.event.pull_request.state == 'open' | ||
| shell: bash | ||
| run: make BUILD_HARNESS_PATH=/build-harness PACKAGES_PREFER_HOST=true -f /build-harness/templates/Makefile.build-harness pr/auto-format/host | ||
|
|
||
| # Commit changes (if any) to the PR branch | ||
| - name: Commit changes to the PR branch | ||
| if: github.event.pull_request.state == 'open' | ||
| shell: bash | ||
| id: commit | ||
| env: | ||
| SENDER: ${{ github.event.sender.login }} | ||
| run: | | ||
| set -x | ||
| output=$(git diff --name-only) | ||
| if [ -n "$output" ]; then | ||
| echo "Changes detected. Pushing to the PR branch" | ||
| git config --global user.name 'cloudpossebot' | ||
| git config --global user.email '[email protected]' | ||
| git add -A | ||
| git commit -m "Auto Format" | ||
| # Prevent looping by not pushing changes in response to changes from cloudpossebot | ||
| [[ $SENDER == "cloudpossebot" ]] || git push | ||
| # Set status to fail, because the push should trigger another status check, | ||
| # and we use success to indicate the checks are finished. | ||
| printf "::set-output name=%s::%s\n" "changed" "true" | ||
| exit 1 | ||
| else | ||
| printf "::set-output name=%s::%s\n" "changed" "false" | ||
| echo "No changes detected" | ||
| fi | ||
| - name: Auto Test | ||
| uses: cloudposse/actions/github/[email protected] | ||
| # match users by ID because logins (user names) are inconsistent, | ||
| # for example in the REST API Renovate Bot is `renovate[bot]` but | ||
| # in GraphQL it is just `renovate`, plus there is a non-bot | ||
| # user `renovate` with ID 1832810. | ||
| # Mergify bot: 37929162 | ||
| # Renovate bot: 29139614 | ||
| # Cloudpossebot: 11232728 | ||
| # Need to use space separators to prevent "21" from matching "112144" | ||
| if: > | ||
| contains(' 37929162 29139614 11232728 ', format(' {0} ', github.event.pull_request.user.id)) | ||
| && steps.commit.outputs.changed == 'false' && github.event.pull_request.state == 'open' | ||
| with: | ||
| token: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }} | ||
| repository: cloudposse/actions | ||
| event-type: test-command | ||
| client-payload: |- | ||
| { "slash_command":{"args": {"unnamed": {"all": "all", "arg1": "all"}}}, | ||
| "pull_request": ${{ toJSON(github.event.pull_request) }}, | ||
| "github":{"payload":{"repository": ${{ toJSON(github.event.repository) }}, | ||
| "comment": {"id": ""} | ||
| } | ||
| } | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters