Skip to content

400 Bad Request for any command #631

Description

Expected Behavior

I expect to be able to see my orgs, programs, etc. I also expect to be able to access (read/write) configuration for them.

Actual Behavior

Any command returns Error: 400 (Bad Request)

Reproduction Scenario, Platform, and Version

npm --version
8.1.3

aio -v
@adobe/aio-cli/8.2.0 darwin-x64 node-v14.16.0

aio plugins
@adobe/aio-cli-plugin-cloudmanager 2.26.1

If this is related to authentication, include the output of aio config:get ims.contexts.aio-cli-plugin-cloudmanager but do not include the private key content or any access tokens.

Output of aio config:get ims.contexts.aio-cli-plugin-cloudmanager is nothing, not even a blank line.

Steps to Reproduce

Steps to reproduce the behavior:

  1. npm install -g @adobe/aio-cli
  2. aio plugins:install @adobe/aio-cli-plugin-cloudmanager
  3. aio plugins:update
  4. aio auth:login Followed by the program opening a browser, logging in, and seeing the Adobe I/O success message.
  5. aio cloudmanager:org:list <- returns Error: 400 (Bad Request)
  6. aio cloudmanager:org:select <- returns Error: 400 (Bad Request)

No activity

Activity on this issue will appear here.

Activity

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions