https://pulumi.com logo
Powered by
Title
n

narrow-cpu-35517

03/27/2023, 9:06 AM
locally it runs fine, and all the aws credentials are also correct in the git actions
s

steep-toddler-94095

03/28/2023, 4:53 AM
does your cluster have a public API endpoint?
n

narrow-cpu-35517

03/30/2023, 12:03 AM
not public, its behind the aws load balancer
but I am providing the id and access tokens for it to connect to the aws account-- in the previous step in the github actions, I read from ECR and that works completely fine
- name: Run pulumi up for stack
        uses: pulumi/actions@v3
        with:          
          command: up
          stack-name: layup/dev
          work-dir: ./pulumi-services-infra        env:
          PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
          #PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}
          APP_VERSION: ${{ steps.build-image.outputs.APP_VERSION}}
          #AWD_PROFILE: dev-admin
          AWS_ACCESS_KEY: ${{ secrets.AWS_ACCESS_KEY_ID_DEV_ADMIN }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY_DEV_ADMIN }}
          AWS_REGION: us-east-1
if I add 
args: --skip-preview
it then completes as it doesn't try to connect to cluster, but I still wonder why
4 Views
#generalJoin Slack
Powered by