Bootstrapping users/groups

[Jesper_Volkers]

Hi Ate, thanks for your reply!

@ate.douma

-Drepo.bootstrap=full should practically never be needed, its mainly provided for specific scenarios in unit tests etc.
-Drepo.bootstrap=true will only apply differences between your current loaded yaml configuration and the previous stored mainline configuration, while -Drepo.bootstrap=full will simply (re)apply all the current loaded yaml configuration. The latter thus will also overwrite (replace) any runtime (config) changes made, not reflected in the mainline configuration.
For production you should never need and use -Drepo.bootstrap=full as you then will lose any runtime changes!

Ye exactly, that’s what I thought too, we always use -Drepo.bootstrap=true so that’s ok

@ate.douma

For the #1 question, your provided yaml configuration actually looks fine to me, so something else must go wrong here. Please double check any warnings logged as anything skipped/ignored typically does get logged.

Error/warning wise we are only getting one ERROR → ERROR [org.onehippo.cm.engine.ConfigurationContentService.apply():174] Processing 'APPEND' action for content node '/content/documents/hippo-project/config/mail' failed.
This is because we changed something in our content, but it will not be processed. Personally it looks more like an warning to me, but maybe I see this wrong? If I want to change content locally, I should have done this in the development module, but still, nothing is breaking right?

@ate.douma

Finally, concerning the groovy updater: can you show your yaml config to load the script + parameters?
And why did you define the parameters separately in json, not within the yaml file?
Also note that any children of the hippo:queue node will be treated as content, so change detection is not relevant (done) on them. But as the updater is supposed to process (and then empty) the queue, there shouldn’t be existing scripts in the queue at startup anyhow.

My ResourceBundleUpdater.yaml:

definitions:
  config:
    /hippo:configuration/hippo:update/hippo:queue/ResourceBundleUpdater:
      jcr:primaryType: hipposys:updaterinfo
      hipposys:batchsize: 100
      hipposys:description: "The ResourceBundleUpdater can be used to \r\n1. Add new labels\
         \ to an EXISTING resource bundle\r\n2. Update existing labels from an EXISTING\
         \ resource bundle\r\n3. Remove labels from an EXSITING resource bundle\r\n\r\n\
         JSON Structure should be:\r\n{\"bundleId\": {\"resourceKey\": \"resourceValue\"\
         }}\r\n\r\nFor removing labels, set value to \"DELETE\""
      hipposys:dryrun: false
      hipposys:parameters:
        type: string
        resource: ResourceBundleUpdater.json
      hipposys:query: /jcr:root/content/documents/hippo-project/config/label//element(*,resourcebundle:resourcebundle)
      hipposys:script:
        type: string
        resource: ResourceBundleUpdater.groovy
      hipposys:throttle: 500
      hipposys:loglevel: DEBUG

This yaml loads the updater into the queue, so that work’s fine, only when making changes in the ResourceBundleUpdater.json, those are not processed.
The reason for using a json file is readability, since these values have to be changed quite often.

… I just see your other replies incoming I didn’t know that we should move the updaters to the hcm-content module. Why should the updaters be part of the content? I think we, developers, should be in control of these scripts right? Can I mark them somehow, so they will be reloaded automatically? Maybe with something like .meta:category: config?