Implement manual prefix setting for configuration ldap

[docjyJ]

• Needed for: use nextcloud_exec_commands to configure LLDAP all-in-one#6909

Summary

This allows you to manually define an LDAP configuration prefix. This is useful for scripts.

The scripts know the prefix and can manage their configuration without interacting with other configurations.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

[docjyJ]

This is my first PR on the repo server, so please feel free to give feedback.

[come-nc]

Why not use the returned prefix in your script instead?
When using occ ldap:create-empty-config --only-print-prefix, the only output is the prefix and you can then store that in a variable in your script.

[docjyJ]

Why not use the returned prefix in your script instead?
When using occ ldap:create-empty-config --only-print-prefix, the only output is the prefix and you can then store that in a variable in your script.

There are two reasons related to the operation of AIO community containers:

• You can't use VAR=$(cmd), is that right, @szaimen?
• The configuration updates each time the system is restarted.

For these reasons, it would be useful to have an identifier known in advance.

[docjyJ]

Adding this feature could lead to inappropriate behaviour if a user creates an s99 configuration and then a configuration with an automatically generated prefix.

Maybe prefixes should be generated in a way that makes them unique (e.g. uuid).

[szaimen]

• You can't use VAR=$(cmd), is that right, @szaimen?

Currently you cannot afaik but I guess we could add support for it...

[docjyJ]

Currently you cannot afaik but I guess we could add support for it...

That shouldn't solve the update problem.

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

[come-nc]

Adding this feature could lead to inappropriate behaviour if a user creates an s99 configuration and then a configuration with an automatically generated prefix.

Maybe prefixes should be generated in a way that makes them unique (e.g. uuid).

For this reason and other potential pitfalls I prefer to stay away from manually set prefix, LDAP configuration prefixes should stay automated.
The command already outputs the new prefix to help with scripting.