Skip to content

Cannot deploy: you are not currently logged in #33

Open

Description

@arpecop
name: Deploy
on:
    push:
        branches:
            - master
jobs:
    deploy:
        name: Deployment
        runs-on: ubuntu-latest
        strategy:
            matrix:
                stages:
                    - stage: 'prod'
                      AWS_SECRET_ACCESS_KEY: 'AWS_SECRET_ACCESS_KEY_PROD'
                      AWS_ACCESS_KEY_ID: 'AWS_ACCESS_KEY_ID_PROD'
        steps:
            - name: Checkout
              uses: actions/checkout@v2
            - name: npm install and build
              run: npm install
            - name: Install VPC Plugin and Deploy
              uses: serverless/github-action@v1.53.0
              with:
                  args: -c "serverless deploy --stage=${{ matrix.stages.stage }} --verbose"
                  entrypoint: /bin/bash
              env:
                  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
                  AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

Screenshot 2020-06-26 at 17 21 19

I added GitHub to serverless and my repos are listing there

Activity

  1. nclaveeoh commented on Aug 8, 2020

    @nclaveeoh

    I ran into the same problem using the AWS key approach, go with SERVERLESS_ACCESS_KEY instead. Go here to see how to create a serverless access key: https://www.serverless.com/framework/docs/dashboard/cicd/running-in-your-own-cicd/

  2. changed the title [-]Cannot deploy [/-] [+]Cannot deploy: you are not currently logged in[/+] on Jan 3, 2021
  3. marcelloromani commented on May 19, 2022

    @marcelloromani

    Also check whether you have

    #app: your-app-name
    #org: your-org-name
    

    defined in serverless.yaml

    I had, but they were wrong: removing those keys altogether fixed the "you are not logged in" issue for me.

  4. AlexRypun commented on Jun 5, 2022

    @AlexRypun

    I had the same issue while deploying with bitbucket pipelines (worked fine from the local machine).
    The removal of "org: *****" from serverless.yml solved the problem.

    Any ideas where the root of the problem is?

  5. magiskboy commented on Feb 1, 2024

    @magiskboy

    I had the same issue while deploying with bitbucket pipelines (worked fine from the local machine). The removal of "org: *****" from serverless.yml solved the problem.

    Any ideas where the root of the problem is?

    it worked for me

  6. ryanlawson commented on May 18, 2024

    @ryanlawson

    If you want to use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY you need to add --use-local-credentials in your args.

  7. ryanlawson commented on May 18, 2024

    @ryanlawson

    Created #90 to add specific options for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions