Feature #3790
Tool should have an upload capability
| Status: | Accepted | Start date: | 05/18/2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | module tool | Spent time: | - | |
| Target version: | - | |||
| Keywords: | Affected URL: | |||
| Branch: | ||||
| Votes: | 5 |
Related issues
History
Updated by Igal Koshevoy about 2 years ago
- Status changed from Unreviewed to Accepted
- Priority changed from Normal to Low
Luke and Michael agreed that we can put a low priority on implementing functionality in the tool that the user can get through the site, other than “search” which is must-have.
To make uploading from the tool, we need to implement feature #3777 “Tool should encode types and dependencies into a release” first, because this vital information isn’t part of the current metadata format.
Updated by David Schmitt almost 2 years ago
My workstation is far removed from the server where I’m developing my modules. Neither fetching the tgz to my local workstation, nor uploading via w3m from the server are really convenient.
Updated by James Turnbull almost 2 years ago
David – what do have an approach in mind or you don’t like the feature at all?
I personally like the idea of an upload function but I have HTTP/HTTPS access from the server to the Forge.
Updated by Igal Koshevoy almost 2 years ago
- Tracker changed from Bug to Feature
Updated by Igal Koshevoy almost 2 years ago
- Assignee deleted (
Igal Koshevoy)
Updated by Alessandro Franceschi over 1 year ago
One of the reasons why I personally I haven’t published many modules on the Forge is that I can’t do them via the tool (eg: via command line). I think that being able to upload modules via the tool is important both for having up to date modules uploaded, both, generally, for a wider usage by users.
My 2c
Igal Koshevoy wrote:
Luke and Michael agreed that we can put a low priority on implementing functionality in the tool that the user can get through the site, other than “search” which is must-have.
To make uploading from the tool, we need to implement feature #3777 “Tool should encode types and dependencies into a release” first, because this vital information isn’t part of the current metadata format.
Updated by Luke Kanies about 1 year ago
No way this should be low priority, either.
Updated by Raphaël Pinson 28 days ago
This would be very useful. Are there any news on this feature?
Updated by Dan Bode 12 days ago
I recently asked a community member if they would publish a module that I wanted to use to the forge and they indicated that this issue was the #1 issue preventing them from publishing their modules to the forge.
Updated by James Turnbull 12 days ago
- Status changed from Accepted to Needs Decision
- Assignee set to Nigel Kersten
Nigel – I think the priority on this ticket is wrong and it seems stalled.
Updated by Alessandro Franceschi 12 days ago
James Turnbull wrote:
Nigel – I think the priority on this ticket is wrong and it seems stalled.
Definitively. For whatever it may count, I add myself to the list of users that would publish on the Forge but don’t do it (or do it rarely) because the upload process is manual and painful. How do you think people will keep modules updated on the Forge if they have to pack them, move them from servers to local desktops, upload via a browser every time they make a relevant change ? Either this or #3874 (and possibly both) are strongly needed, imvho.
Updated by Peter Meier 12 days ago
Dan was referring to my little “rant” @ github.
So, I just like to second what Alessandro said.
I think it’s something that a lot of people are waiting for.
Updated by Nigel Kersten 12 days ago
- Status changed from Needs Decision to Accepted
- Priority changed from Low to High
Yeah, this ticket doesn’t reflect reality.
We’re running through a quick specification process this afternoon to add publishing mechanisms to the command line tool. We’ll get the results of that posted here and on the public user lists ASAP.
Adding Pieter to watch the ticket as he’s working on this too.
Updated by Nigel Kersten 12 days ago
I’ll also add that it’s become a little confusing where tickets live now that the puppet module tool is part of core Puppet…