Hide Forgot
Description of problem: Extend rhq:archive and rhq:file tasks to allow fetching them over an URL. That way, there is no need upload files to RHQ server for using provisioning feature. Use Case: Provision JBoss Application Server A customized JBoss AS binary can be uploaded to a central repository ( may be as simple as Apache HTTP server or even Subversion ). This can then be used to provision JBoss AS on various platforms using the same file from central repository. Different deployment tasks like provisioning of JBoss AS with default profile, with clustered profile or a stripped down profile can use the same file via URL.
mazz/jshaughn - do we support, and if not, what would it take?
I actually have a branch locally on my box where I started this work. It isn't close to being complete, though. Its doable, its just finding time to do it. Less than a week worth of work I'm guessing.
bug 610876 duplicated this issue. Here's my comments from that dup'ed issue (which I will close to leave only this issue open). --- some ant recipe's might not want bundle files stored in RHQ uploaded by a user. There might be bundle files that already exist in a user's existing infrastructure (like a apache server or a code repository) accessible via a URL. Be able to specify in the recipe archive and raw files that come from a URL. Be able to have ${var} notation in the URL. example: <rhq:deployment-unit> <rhq:url-file url="http://foo/${user.config.prop}.properties" destinationFile="subdir/${user.config.prop}.properties" replace="true"/> <rhq:url-archive url="http://${server.host.prop}/file.zip"> ... Notice that <rhq:url-file> has the same semantics as <rhq:file> - with the name attribute replaced with a "url" attribute - it just gets the content of the file from the URL rather than the local disk at ${basedir}. Notice that <rhq:url-archive> has the same semantics as <rhq:archive> - with the name attribute replaced with a "url" attribute - it just gets the content of the archive from the URL rather than the local disk at ${basedir}. An optional further enhancement would be to support credentials of the URL is secured. Would probably also need to support this kind of feature in the file template recipe type, though not as critical.
*** Bug 610876 has been marked as a duplicate of this bug. ***
I have the start of this on my local box... though it isn't close to complete.
this is important to implement for those people that have large bundles that they don't want stored in RHQ's own data store. The bundles might already exist somewhere else (in some git repo, or apache server, as two examples) - they just want to use that rather store duplicates in RHQ. (note to self: can we use content sources for this? just a thought)
master commit: 9f09183904e6c03dc81b058f715a12ce02bc662c for docs on how to put this in your ant recipe and test, see: http://rhq-project.org/display/JOPR2/Ant+Bundles#AntBundles-rhq%3Aurlarchive http://rhq-project.org/display/JOPR2/Ant+Bundles#AntBundles-rhq%3Aurlfile
Verified on build#123 (Version: 4.1.0-SNAPSHOT Build Number: a6d2d56) Created a recipe with rhq:url-file url and rhq:url-archive url tasks to allow fetching them over an URL. Please refer the attached recipe. Created and deployed the bundle successfully. Marking as verified.
Created attachment 504641 [details] Test recipe
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.