docs: clean up action comments — describe what we do, not what others had
This commit is contained in:
@@ -1,12 +1,9 @@
|
||||
# Tinqs Setup AWS — replaces aws-actions/configure-aws-credentials@v4
|
||||
# Original: https://github.com/aws-actions/configure-aws-credentials (GitHub-hosted, Node.js)
|
||||
# Why rewritten: Original uses OIDC federation with GitHub's token endpoint — doesn't exist
|
||||
# on Gitea. Our runners use IAM task roles (ECS/Fargate) or instance profiles (EC2/Lightsail),
|
||||
# so we don't need credential configuration — just install the CLI and optionally ECR login.
|
||||
# Removed from original: OIDC, assume-role, session tokens, credential masking, region output.
|
||||
# ECR login bundled here instead of needing separate aws-actions/amazon-ecr-login.
|
||||
# Author: Ozan / Claude Code — 2026-05-22
|
||||
# Part of: tinqs/ci (Tinqs CI toolchain)
|
||||
# tinqs/ci/setup-aws — Tinqs Studio CI
|
||||
# Installs AWS CLI and optionally logs into ECR.
|
||||
# Credentials come from the runner environment (IAM task role on Fargate, instance
|
||||
# profile on EC2/Lightsail) — no explicit key configuration needed.
|
||||
# Composite action — runs directly on the host.
|
||||
# Author: Ozan + Claude Code — 2026-05-22
|
||||
|
||||
name: 'Tinqs Setup AWS'
|
||||
description: 'Install AWS CLI and optionally login to ECR'
|
||||
|
||||
Reference in New Issue
Block a user