Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N nrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • 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
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • argo
  • nrm
  • Issues
  • #8
Closed
Open
Issue created May 30, 2018 by Sridutt Bhalachandra@sriduttbContributor

Bad relative path handling between command line client and daemon

If the command line client is provided a manifest file by relative path e.g. ./doc/manifest, the path is provided as is to the daemon, which is probably not in the current working directory. This can trigger File not found errors on the daemon side.

2 possible solutions:

  • resolve the absolute path in the cli tool, and check that the file exists, before giving it to the daemon
  • read the manifest in the cli tool, and provide the manifest info to the daemon as a command argument.

The second solution is probably cleaner for the long term.

Edited May 30, 2018 by Swann Perarnau
Assignee
Assign to
Time tracking