No objection from my side.
Regards
JB
On Wed, Aug 24, 2022 at 1:16 PM Francesco Chicchiriccò
wrote:
>
> Hi all,
> working for SYNCOPE-1692, which involves some changes in the provisioning
> process, I've realized that the Camel Provisioning Manager extension [1],
> while featuring some very
github-code-scanning[bot] commented on code in PR #370:
URL: https://github.com/apache/syncope/pull/370#discussion_r953914138
##
core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/AbstractValueSerializer.java:
##
@@ -0,0 +1,64 @@
+/*
+ *
ilgrosso opened a new pull request, #370:
URL: https://github.com/apache/syncope/pull/370
Missing:
- [ ] additional tests
- [ ] docs update
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
In general, I am in favor of this approach, but just to be on the safe
side, would it make sense to deprecate the feature first? Just in case
someone out there is using it, or would keeping the code around cause
complications and maintenance issues?
On Wed, Aug 24, 2022 at 4:16 AM Francesco
Hi all,
working for SYNCOPE-1692, which involves some changes in the provisioning
process, I've realized that the Camel Provisioning Manager extension [1], while
featuring some very smart code has probably never been used in any production
deployment, at least none that I am aware of.
Over
