Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N neutrinet_cube_install
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • 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
  • Neutrinet
  • neutrinet_cube_install
  • Issues
  • #24
Closed
Open
Created Jan 20, 2020 by HgO@HgOOwner

Issues with the cleanup function when aborting

There are two bugs with the cleanup function when we interrupt the script:

  • After a read -s, the user inputs are kept hidden (e.g, try Ctrl+C after a password prompt)
  • After the prompt for sudo password, the user is not asked to remove the resources. This is because at this point in the script, we are in the cube_resources folder, so the cleanup function is checking to remove resources that would be located relatively to this folder... Solution is to use absolute paths.
Edited Jan 20, 2020 by HgO
Assignee
Assign to
Time tracking