Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F fuss-manager
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 50
    • Issues 50
    • 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
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FUSS
  • fuss-manager
  • Issues
  • #957

Closed
Open
Created Jun 21, 2021 by Enrico Zini@enrico

Usare scritture atomiche in SimpleAnsibleInventory

Al momento una scrittura interrotta dell'inventory di Ansible lascia un file corrotto.

Possiamo cambiare la open con un atomic_writer (preso per esempio da https://salsa.debian.org/nm-team/nm.debian.org/-/blob/master/backend/utils.py#L25 ) per evitare il problema, e sovrascrivere l'inventory di Ansible precedente solo se la scrittura è andata a buon fine

Assignee
Assign to
Time tracking