Files
FahdShalhoub 0cfd89f200
Build, Push and Deploy CMS / build-push-deploy (push) Successful in 2m28s
Deploy Infrastructure / pulumi-up (push) Successful in 2s
FEAT: Return Playback URL in Get Videos
2026-08-27 21:31:13 +03:00

37 lines
1.8 KiB
YAML

# The LocalStack target for the same program that deploys production. Nothing
# here changes what the code does except thamanyah:localstack — every AWS
# endpoint override lives in the aws:* provider config, which the AWS provider
# reads on its own.
#
# localhost.localstack.cloud resolves to 127.0.0.1 in public DNS, and
# docker-compose.yml also publishes it as a network alias for the localstack
# container — so this one endpoint works whether pulumi runs on the host or as
# the compose "infra" service.
config:
aws:region: us-east-1
aws:accessKey: test
aws:secretKey: test
aws:skipCredentialsValidation: "true"
# SNS builds topic ARNs from the caller's account id, so unlike the other
# services it cannot work without one — "true" here makes the provider hand
# SNS an empty account and every topic call fails. sts is pointed at
# LocalStack just below, so asking is cheap and answers 000000000000.
aws:skipRequestingAccountId: "false"
aws:skipMetadataApiCheck: "true"
# Virtual-host addressing would resolve <bucket>.localhost.localstack.cloud,
# which points at 127.0.0.1 — the wrong container from inside compose.
aws:s3UsePathStyle: "true"
aws:endpoints:
- iam: http://localhost.localstack.cloud:4566
rds: http://localhost.localstack.cloud:4566
s3: http://localhost.localstack.cloud:4566
# aws@7 reads a bucket's tags back through S3 Control's
# ListTagsForResource, so without this override the create call
# goes to real AWS and 403s — even though no tags are set here.
s3control: http://localhost.localstack.cloud:4566
sns: http://localhost.localstack.cloud:4566
sqs: http://localhost.localstack.cloud:4566
sts: http://localhost.localstack.cloud:4566
thamanyah:localstack: "true"
encryptionsalt: v1:QKoqcSNBvDc=:v1:bTGZko5jHuGNRVoq:2oQ4pFb8MYwspEbxipYeO+rVqVnLBg==