Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.core
beat.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.corebeat.core
  • Issues
  • #93

Closed
Open
Opened Jan 29, 2020 by Samuel GAIST@samuel.gaist
  • Report abuse
  • New issue
Report abuse New issue

New environment descovery does not respect the raise on error property

If the discovery process using image labels is run on a machine without docker running or if the daemon is not running, it will fail as expected however the error handling does not follow the raise on error property.

To reproduce, call beat editor refresh-env on a machine without docker or with the daemon stopped.

A current workaround is to create the .environments.json file in the prefix with {} as its content.

Assignee
Assign to
Soft loops
Milestone
Soft loops
Assign milestone
Time tracking
None
Due date
None
2
Labels
bug confirmed
Assign labels
  • View project labels
Reference: beat/beat.core#93