Bug 610876
| Summary: | be able to have ant recipe specify URL based bundle files | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
| Component: | Provisioning | Assignee: | John Mazzitelli <mazz> |
| Status: | CLOSED DUPLICATE | QA Contact: | Corey Welton <cwelton> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-13 18:12:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
bumping to medium priority - this would be a helpful feature side note: I would like to add url-type commands to the file template bundle type's recipe as well. Triaged 24-Sept *** This bug has been marked as a duplicate of bug 609154 *** |
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.