juju resources needs to support extensions other than ".tgz"

Bug #1585701 reported by Matt Bruzek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Invalid
Undecided
Katherine Cox-Buday

Bug Description

I am trying to write docs for the resources feature and I found that ".zip" is not a valid extension.

```
juju deploy ../trusty/resources-example --series trusty --resource software=consul_0.6.4_linux_amd64.zip
ERROR PUT https://54.165.203.172:17070/model/222633d3-247a-474a-88dc-8c7a501fe3a7/services/resources-example/resources/software?pendingid=6d9225a8-b75b-44b8-8b95-f3f87262477f: incorrect extension on resource upload "consul_0.6.4_linux_amd64.zip", expected ".tgz"
```

Different software is packaged in a variety of methods. We are not asking our users to repackage their files into tgz just for Juju are we?

I thought resources handled binary blobs. Why does resources even care what extension this file is? Can we fix this?

Revision history for this message
Charles Butler (lazypower) wrote :

+1 support your local zip distributor

Revision history for this message
Katherine Cox-Buday (cox-katherine-e) wrote :

What extension is declared in the charm's metadata.yaml?

Changed in juju-core:
assignee: nobody → Katherine Cox-Buday (cox-katherine-e)
status: New → Incomplete
Revision history for this message
Matt Bruzek (mbruzek) wrote :

yeah I see that I used software.tgz in the metadata.yaml file. Sorry for the noise.

Changed in juju-core:
status: Incomplete → Invalid
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.