GitHub action to run StackSpot Runtime Destroy Worker.
Note: This action is supported on debian/RHEl like systems
Check how to implement the orchestration job using the runtime-manager-action
jobs:
job1:
runs-on: ubuntu-latest
needs: [orchestration]
strategy:
matrix:
task: ${{ fromJSON(needs.orchestration.outputs.tasks) }}
fail-fast: true
max-parallel: 1
steps:
- name: DESTROY
if: contains( matrix.task.taskType , 'DESTROY')
uses: stack-spot/runtime-destroy-action@v2
with:
FEATURES_LEVEL_LOG: debug
CLIENT_ID: ${{ secrets.CLIENT_ID }}
CLIENT_KEY: ${{ secrets.CLIENT_KEY }}
CLIENT_REALM: ${{ secrets.CLIENT_REALM }}
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
AWS_SESSION_TOKEN: ${{ secrets.AWS_SESSION_TOKEN }}
AWS_ROLE_ARN: ${{ secrets.AWS_ROLE_ARN }}
AWS_REGION: sa-east-1
REPOSITORY_NAME: my-repository-name
RUN_TASK_ID: ${{ matrix.task.runTaskId }}
CONTAINER_URL: my/container-url # not mandatory
FEATURES_TERRAFORM_MODULES: ... # not mandatory
PATH_TO_MOUNT: path/to/mount
LOCALEXEC_ENABLED: true # not mandatory
TF_LOG_PROVIDER: info # not mandatory| Field | Mandatory | Observation |
|---|---|---|
| FEATURES_LEVEL_LOG | YES | Log Level |
| CLIENT_ID | YES | StackSpot Client ID. |
| CLIENT_KEY | YES | StackSpot Client KEY. |
| CLIENT_REALM | YES | StackSpot Client Realm. |
| AWS_ACCESS_KEY_ID | NO | AWS Access Key ID |
| AWS_SECRET_ACCESS_KEY | NO | AWS Secret Access Key |
| AWS_SESSION_TOKEN | NO | AWS Session Token |
| AWS_ROLE_ARN | NO | AWS IAM ROLE (necessary if AWS credentials not informed) |
| AWS_REGION | YES | AWS region where resources with be provisioned. Used for tf backend as well (e.g: us-east-1). |
| RUN_TASK_ID | YES | StackSpot Runtime task id to be executed, according to runtime-manager-action. |
| REPOSITORY_NAME | YES | Repository name to checkout during task process. |
| CONTAINER_URL | NO | Container url reference (e.g stackspot/image) |
| FEATURES_TERRAFORM_MODULES | NO | List of external terraform modules allowed |
| PATH_TO_MOUNT | YES | Path provided to be used as a volume within the docker image that will be used with terraform |
| LOCALEXEC_ENABLED | NO | Whether or not terraform will be enable to perform local exec operations or not (default: false) |
| TF_LOG_PROVIDER | NO | If there is a need to check Terraform's own log, it is now possible to pass the levels of the Terraform provider, allowing you to analyze what happens within Terraform's CLI (info, trace, debug and warn). |