Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.cmdline beat.cmdline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.cmdlinebeat.cmdline
  • Issues
  • #64
Closed
Open
Issue created Jan 29, 2020 by Samuel GAIST@samuel.gaistOwner

Do not make the environment listing failed if platform is unavailable

As implemented, the environment listing should not fail for local docker environment but it is currently not the case for listing the remote environment.

Both should behave the same. Therefore, if any error happens when contacting the platform, it should be logged and the command continue showing an empty set of environment coming from there.

Assignee
Assign to
Time tracking