[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129993#comment-15129993 ] Carsten Ziegeler commented on SLING-5414: - The model parser is a bundle which can easily be used within your app. Not sure about how to get the prov model > Make the contents of the provisioning model available at runtime > > > Key: SLING-5414 > URL: https://issues.apache.org/jira/browse/SLING-5414 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes >Affects Versions: Slingstart Maven Plugin 1.4.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Slingstart Maven Plugin 1.4.2 > > Attachments: SLING-5414.patch > > > For SLING-5355 we need to make additional sections from the provisioning > model available at runtime, so that ACLs can be set at startup, and also to > be able to reuse their definitions later for auditing/verification purposes. > A simple way to do that is to copy those sections in the sling_bootstrap.txt > file. I have created a patch that does that, will attach it here for review. > _edit: as discussed below, we'll make the full text of the model available at > runtime_ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[
https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130378#comment-15130378
]
Oliver Lietz commented on SLING-5414:
-
Right. For provisioning on Karaf it's {{feature.xml}} and an additional
configuration ({{karaf-maven-plugin}}) in a POM for building a Karaf-based
Sling distribution.
> Make the contents of the provisioning model available at runtime
>
>
> Key: SLING-5414
> URL: https://issues.apache.org/jira/browse/SLING-5414
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
>Affects Versions: Slingstart Maven Plugin 1.4.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Slingstart Maven Plugin 1.4.2
>
> Attachments: SLING-5414.patch
>
>
> For SLING-5355 we need to make additional sections from the provisioning
> model available at runtime, so that ACLs can be set at startup, and also to
> be able to reuse their definitions later for auditing/verification purposes.
> A simple way to do that is to copy those sections in the sling_bootstrap.txt
> file. I have created a patch that does that, will attach it here for review.
> _edit: as discussed below, we'll make the full text of the model available at
> runtime_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[
https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130078#comment-15130078
]
Bertrand Delacretaz commented on SLING-5414:
I'm fine with releasing as is, providing the model to the launchpad but medium
term my idea is to
* a) Generate a fragment bundle at build time, that contains the provisioning
model, and inject it in the model
* b) Provide an API to retrieve and parse the provisioning model at runtime.
The bundle that does this uses the fragment bundle created by a)
I've tried both at
https://datatracker.ietf.org/doc/draft-ietf-appsawg-http-problem/ but I'm not
happy with the implementation of a) there, need to revisit this. On the other
hand the (trivial) {{bundles/extensions/provisioning-model-provider}} that's
there could stay as is once a) works. I probably won't have time to work again
on this before a week, so I'm fine releasing the slingstart plugin as is if
that's useful.
> Make the contents of the provisioning model available at runtime
>
>
> Key: SLING-5414
> URL: https://issues.apache.org/jira/browse/SLING-5414
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
>Affects Versions: Slingstart Maven Plugin 1.4.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Slingstart Maven Plugin 1.4.2
>
> Attachments: SLING-5414.patch
>
>
> For SLING-5355 we need to make additional sections from the provisioning
> model available at runtime, so that ACLs can be set at startup, and also to
> be able to reuse their definitions later for auditing/verification purposes.
> A simple way to do that is to copy those sections in the sling_bootstrap.txt
> file. I have created a patch that does that, will attach it here for review.
> _edit: as discussed below, we'll make the full text of the model available at
> runtime_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129982#comment-15129982 ] Felix Meschberger commented on SLING-5414: -- >From the peanut gallery: Providing the model is ok. Do we also have API to >expose this model programmatically ? Such that not everyone goes about trying >to find the model and parse the model ... > Make the contents of the provisioning model available at runtime > > > Key: SLING-5414 > URL: https://issues.apache.org/jira/browse/SLING-5414 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes >Affects Versions: Slingstart Maven Plugin 1.4.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Slingstart Maven Plugin 1.4.2 > > Attachments: SLING-5414.patch > > > For SLING-5355 we need to make additional sections from the provisioning > model available at runtime, so that ACLs can be set at startup, and also to > be able to reuse their definitions later for auditing/verification purposes. > A simple way to do that is to copy those sections in the sling_bootstrap.txt > file. I have created a patch that does that, will attach it here for review. > _edit: as discussed below, we'll make the full text of the model available at > runtime_ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129968#comment-15129968 ] Carsten Ziegeler commented on SLING-5414: - [~bdelacretaz] I would like to release the slingstart maven plugin - what's the status here? > Make the contents of the provisioning model available at runtime > > > Key: SLING-5414 > URL: https://issues.apache.org/jira/browse/SLING-5414 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes >Affects Versions: Slingstart Maven Plugin 1.4.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Slingstart Maven Plugin 1.4.2 > > Attachments: SLING-5414.patch > > > For SLING-5355 we need to make additional sections from the provisioning > model available at runtime, so that ACLs can be set at startup, and also to > be able to reuse their definitions later for auditing/verification purposes. > A simple way to do that is to copy those sections in the sling_bootstrap.txt > file. I have created a patch that does that, will attach it here for review. > _edit: as discussed below, we'll make the full text of the model available at > runtime_ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129972#comment-15129972 ] Carsten Ziegeler commented on SLING-5414: - [~olli], [~bdelacretaz] I think the current approach is fine - this is about storing the provisioning model in launchpad; if the instance is built using something else like Karaf there is no provisioning model. Or maybe I'm missing something? > Make the contents of the provisioning model available at runtime > > > Key: SLING-5414 > URL: https://issues.apache.org/jira/browse/SLING-5414 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes >Affects Versions: Slingstart Maven Plugin 1.4.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Slingstart Maven Plugin 1.4.2 > > Attachments: SLING-5414.patch > > > For SLING-5355 we need to make additional sections from the provisioning > model available at runtime, so that ACLs can be set at startup, and also to > be able to reuse their definitions later for auditing/verification purposes. > A simple way to do that is to copy those sections in the sling_bootstrap.txt > file. I have created a patch that does that, will attach it here for review. > _edit: as discussed below, we'll make the full text of the model available at > runtime_ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105105#comment-15105105 ] Bertrand Delacretaz commented on SLING-5414: I've tried an approach where the slingstart maven plugin generates a bundle with a "modelfragment" classifier, used by a provisioning model provider bundle to supply the model at runtime. It works but creates a "chicken and egg" dependency on the modelfragment bundle in launchpad/builder. I have saved that variant at https://github.com/bdelacretaz/sling/tree/SLING-5414-wontwork but will need to change the strategy in the slingstart plugin - having that optionally inject the modelfragment bundle in the provisioning model, without having a dependency on it, should work. > Make the contents of the provisioning model available at runtime > > > Key: SLING-5414 > URL: https://issues.apache.org/jira/browse/SLING-5414 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes >Affects Versions: Slingstart Maven Plugin 1.4.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Slingstart Maven Plugin 1.4.2 > > Attachments: SLING-5414.patch > > > For SLING-5355 we need to make additional sections from the provisioning > model available at runtime, so that ACLs can be set at startup, and also to > be able to reuse their definitions later for auditing/verification purposes. > A simple way to do that is to copy those sections in the sling_bootstrap.txt > file. I have created a patch that does that, will attach it here for review. > _edit: as discussed below, we'll make the full text of the model available at > runtime_ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091645#comment-15091645 ] Bertrand Delacretaz commented on SLING-5414: Thanks [~olli] for fixing this, I'll think about a more universal way of providing the model at runtime. > Make the contents of the provisioning model available at runtime > > > Key: SLING-5414 > URL: https://issues.apache.org/jira/browse/SLING-5414 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes >Affects Versions: Slingstart Maven Plugin 1.4.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Slingstart Maven Plugin 1.4.2 > > Attachments: SLING-5414.patch > > > For SLING-5355 we need to make additional sections from the provisioning > model available at runtime, so that ACLs can be set at startup, and also to > be able to reuse their definitions later for auditing/verification purposes. > A simple way to do that is to copy those sections in the sling_bootstrap.txt > file. I have created a patch that does that, will attach it here for review. > _edit: as discussed below, we'll make the full text of the model available at > runtime_ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[
https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090568#comment-15090568
]
Oliver Lietz commented on SLING-5414:
-
This is working with Launchpad/Provisioning Model only, so I've excluded
{{EmbeddedModelTest}} from testing against Karaf (SLING-3821) in
[r1723847|https://svn.apache.org/r1723847]. I wonder if putting the bootstrap
stuff into a dedicated bundle is more flexible and portable across launchers.
> Make the contents of the provisioning model available at runtime
>
>
> Key: SLING-5414
> URL: https://issues.apache.org/jira/browse/SLING-5414
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
>Affects Versions: Slingstart Maven Plugin 1.4.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Slingstart Maven Plugin 1.4.2
>
> Attachments: SLING-5414.patch
>
>
> For SLING-5355 we need to make additional sections from the provisioning
> model available at runtime, so that ACLs can be set at startup, and also to
> be able to reuse their definitions later for auditing/verification purposes.
> A simple way to do that is to copy those sections in the sling_bootstrap.txt
> file. I have created a patch that does that, will attach it here for review.
> _edit: as discussed below, we'll make the full text of the model available at
> runtime_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime
[
https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089349#comment-15089349
]
Bertrand Delacretaz commented on SLING-5414:
Implemented in http://svn.apache.org/r1723740, with an integration test.
The provisioning model dump is now embedded in the launchpad jar under
{{/resources/provisioning/model.txt}}
For now the integration test requires using the latest
{{slingstart-maven-plugin}} snapshot, I have deployed that.
> Make the contents of the provisioning model available at runtime
>
>
> Key: SLING-5414
> URL: https://issues.apache.org/jira/browse/SLING-5414
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
>Affects Versions: Slingstart Maven Plugin 1.4.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Slingstart Maven Plugin 1.4.2
>
> Attachments: SLING-5414.patch
>
>
> For SLING-5355 we need to make additional sections from the provisioning
> model available at runtime, so that ACLs can be set at startup, and also to
> be able to reuse their definitions later for auditing/verification purposes.
> A simple way to do that is to copy those sections in the sling_bootstrap.txt
> file. I have created a patch that does that, will attach it here for review.
> _edit: as discussed below, we'll make the full text of the model available at
> runtime_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
