Disable control API in fleet deploy workflow
CI user cannot create IAM roles/users required for the control API. Keep TF_VAR_control_api_enabled=false so fleet AMI redeploys are reliable.
This commit is contained in:
parent
0f7e6570eb
commit
9d1ee1023e
6
.github/workflows/fleet-deploy.yml
vendored
6
.github/workflows/fleet-deploy.yml
vendored
@ -27,9 +27,9 @@ jobs:
|
||||
TF_BACKEND_KEY: state/clawdinators.tfstate
|
||||
TF_BACKEND_REGION: ${{ secrets.AWS_REGION }}
|
||||
TF_BACKEND_DYNAMO_TABLE: clawdinator-terraform-locks
|
||||
TF_VAR_control_api_enabled: true
|
||||
TF_VAR_control_api_token: ${{ secrets.CONTROL_API_TOKEN }}
|
||||
TF_VAR_github_token: ${{ secrets.CLAWDINATOR_WORKFLOW_TOKEN }}
|
||||
# Control API is optional and requires broader IAM privileges than the CI user has.
|
||||
# Keep disabled for fleet AMI redeploys.
|
||||
TF_VAR_control_api_enabled: false
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v4
|
||||
|
||||
Loading…
Reference in New Issue
Block a user