The environment used when creating the snap.yaml should be controlled by meta

Bug #1791985 reported by Kyle Fazzari
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Status tracked in Trunk
Fix Committed
Kyle Fazzari
Fix Released
Kyle Fazzari

Bug Description

Today there's only a single environment used when generating the snap's snap.yaml, and it's set by the Lifecycle. However, as we move toward having separate environments per lifecycle step, generating the snap.yaml will involve using multiple environments. As a result, the environment should be controlled by meta instead of the lifecycle.

Revision history for this message
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
status: New → Fix Committed
importance: Undecided → Wishlist
assignee: nobody → Kyle Fazzari (kyrofa)
milestone: none → 2.44
tags: added: 18.10-templates
Kyle Fazzari (kyrofa)
tags: added: 18.10-extensions
removed: 18.10-templates
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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