Maven global archetype: Differentiate between the user to deploy packages and the user to deploy bundles
Description
Activity
Show:
Stefan Seifert April 27, 2020 at 2:52 PM
PR merged
Henry Kuijpers April 27, 2020 at 2:19 PM
Yes, this is exactly how I envisioned it to be done! Looks good to me!
Stefan Seifert April 27, 2020 at 1:39 PM
sounds reasonable - i've provided a PR with my proposal:
https://github.com/wcm-io/wcm-io-tooling/pull/29
can you have a quick look if it solves your problem? i want to release a new version aem-global-parent very soon
Fixed
Details
Details
Assignee
Stefan SeifertReporter
Henry KuijpersLabels
Components
Fix versions
Priority
MajorCreated April 24, 2020 at 10:53 AM
Updated April 30, 2020 at 8:44 PM
Resolved April 27, 2020 at 2:52 PM
Since the bundle deployment is done through the OSGi console, our "deployer" user is unable to send an OSGi bundle to be deployed to /system/console. However, we do need to use this user to deploy content packages, since we do not want to use the admin user.
We're not using the admin-user, since we're also not using the admin user on higher environments to do the deployment, in order to keep our development process as close as possible to the production way of deploying, to be able to spot errors/issues earlier.
It would be nice to be able to make the user configuration two-fold:
User and password to use when deploying a bundle (in case it is done through the OSGi console);
User and password to use when deploying a content package (or bundle through Sling).
Or maybe it's possible to be able to use Sling for uploading the bundle, instead of doing it through the OSGi console? Though this bug/feature: http://apache-sling.73963.n3.nabble.com/Issue-using-PUT-with-maven-sling-plugin-and-non-existent-path-td3885587.html will need to be fixed then.