FOUND_CHARM is not set correctly for reactive charms

Bug #1767240 reported by Barry Price
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charm Test
Invalid
Undecided
Unassigned

Bug Description

Running "charm build" for a reactive charm results in the keys and values within metadata.yaml becoming quoted.

So this:

$ grep name metadata.yaml
name: canonical-livepatch

becomes this:

$ grep name metadata.yaml
"name": "canonical-livepatch"

Which means this:

FOUND_CHARM=$(find . -maxdepth 1 -name metadata.yaml | xargs grep '^name' | awk '{print $2}')

will not find anything.

I'll put an MP together shortly, should be a trivial fix

Barry Price (barryprice)
Changed in charm-test:
assignee: nobody → Barry Price (barryprice)
status: New → In Progress
description: updated
Revision history for this message
Barry Price (barryprice) wrote :

Ah ignore this, just realised this isn't intended for built charms...

Changed in charm-test:
status: In Progress → Invalid
assignee: Barry Price (barryprice) → nobody
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.