Age | Commit message (Collapse) | Author | Files | Lines |
|
When serveral targets were set in the widget file, the
framework allocated the same HTTP port to each. This
lead to impossibility to run all targets or to a
systemd conflict.
This should fix the issue by allocating an HTTP port for
each target installed by the widget. To achieves that goal,
the afm-unit.conf tag for the port is moved from
'#metadata.http-port' to '#metatarget.http-port'.
Bug-AGL: SPEC-2068
Change-Id: I5376d6f052e0ffc5c77cc80041528637777aed1e
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Export the new variables:
- AFM_ID: the identifier of the application
- AFM_WORKDIR: the workdir of the application
- AFM_WSAPI_DIR: the directory where APIs can
be accessed
Change-Id: I79b46754f84161a36d9a13dd79bc94e777c854fe
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
This commit introduce "tcp", a new type of
provided/required api. It appears in the config.xml
as below:
<urn:AGL:widget:provided-api>
<param "name"="HOST:PORT/API" "value"="tcp">
<urn:AGL:widget:required-api>
<param "name"="HOST:PORT/API" "value"="tcp">
This implementation is a draft. The service
exposed can not start automatically. Use it
with the permission urn:AGL:permission::system:run-by-default.
Change-Id: Ic593f0d891692ca0c777c49057ec54c37fc55cc0
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
This commit introduce two new features:
<urn:AGL:widget:provided-binding>
<param "name"="public-name" "value"="relative-path-to-the-binding"/>
<urn:AGL:widget:required-binding>
<param "name"="public-name" "value"="extern">
<param "name"="relative-path-to-the-binding" "value"="local">
TODO: manage security by setting correct Smack label to the exported files
Bugs-AGL: SPEC-1439
Bugs-AGL: SPEC-1663
Change-Id: I70aad7d523ece7a2ae0058b79708a02ef81144e2
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Iad46596435eebdc5c521b572fd8320b52a61d197
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|