Skip to content

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

Closed
Open
Opened May 30, 2018 by Sridutt Bhalachandra@sriduttb
  • Report abuse
  • New issue
Report abuse New issue

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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: argo/nrm#8