[
https://issues.apache.org/jira/browse/ACE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-162.
----------------------------------
Resolution: Invalid
In the "old" agent, we had already integrated some support for this, but the
new agent can first download and then install a deployment package, making it
much easier by design to support this scenario. Therefore, nothing needs to be
explicitly coded for this anymore.
> Add support for 'file' URLs in the management agent
> ---------------------------------------------------
>
> Key: ACE-162
> URL: https://issues.apache.org/jira/browse/ACE-162
> Project: ACE
> Issue Type: Task
> Components: Management Agent
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
>
> Under normal circumstances, the management agent uses a URL it obtained via
> the Discovery service to communicate with the server (where the URL is the
> base for a series or REST based calls). If the URL uses the 'file' protocol,
> we try to map these requests to the local filesystem:
> Deployments map to a folder structure that is constructed as follows:
> DISCOVERY_URL/deployment/TARGET_ID/versions should be an existing folder,
> containing files that are deployment packages and that are named after their
> versions (with no extension), so '1.0.0', '2.0.0', etc. The deployment
> package metadata must match the folder structure as well.
> Synchronizing the local audit log(s) to the server is not supported, as it
> would make little sense.
> Subscribing to new distributions is not supported either, since that does not
> make sense without a real server.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
