drivers.yaml should live in a writable directory in the snap

Bug #1773576 reported by james beedy
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Status tracked in 3.6
2.4
Won't Fix
High
Andres Rodriguez
3.4
Won't Fix
Medium
Unassigned
3.5
Won't Fix
Medium
Unassigned
3.6
Triaged
Medium
Unassigned

Bug Description

Need to be able to modify drivers.yaml/preseeds to add an entry for a 3rd party drivers repo, but it seems these live in a non writable location.

Can we put drivers.yaml and preseeds under $SNAP_COMMON somewhere?

Thanks

Tags: snap
Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.4.x
tags: added: snap
summary: - drivers.yaml should live in a writable directory
+ [2.4, snap] drivers.yaml should live in a writable directory
Changed in maas:
assignee: nobody → Andres Rodriguez (andreserl)
milestone: 2.4.x → 2.5.0
james beedy (jamesbeedy)
summary: - [2.4, snap] drivers.yaml should live in a writable directory
+ [2.4, snap] drivers.yaml and preseeds should live in a writable
+ directory
description: updated
summary: - [2.4, snap] drivers.yaml and preseeds should live in a writable
- directory
+ [2.4, snap] drivers.yaml should live in a writable directory
Changed in maas:
milestone: 2.5.0 → 2.5.x
Changed in maas:
milestone: 2.5.x → 2.6.0
Alberto Donato (ack)
Changed in maas:
assignee: Andres Rodriguez (andreserl) → nobody
Alberto Donato (ack)
summary: - [2.4, snap] drivers.yaml should live in a writable directory
+ drivers.yaml should live in a writable directory in the snap
Changed in maas:
milestone: 2.6.0 → none
Changed in maas:
importance: High → Medium
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
Changed in maas:
milestone: 3.4.x → 3.5.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.