Keyfactor
Transaction support for signing and timed service
There are use cases, when siging worker needs to be executed in transaction because it interacts with the database. Typically, when the keys are stored in the database, or some other information needs to be updated during signing execution.
This implementation introduces feature to turn on the transaction handling for other use cases then for key usage counter or archiving. Specifically for signing and timed services.
There is a new interface requiresTransaction implemented, which is false by default.
Hi!
This looks very interesting!
There's quite a lot of whitespace/formatting changes that are unrelated to the actual feature. Could you break these out into a separate PR? This makes it easier to track the changes and review the changes.
Thanks!
Hi!
This looks very interesting!
There's quite a lot of whitespace/formatting changes that are unrelated to the actual feature. Could you break these out into a separate PR? This makes it easier to track the changes and review the changes.
Thanks!
It was automatically formatted by IDE I believe, I will try to remove it and keep it clear.
@mlundblad I am just wondering if this PR is ok and will be merged into the main branch. Is there anything I should clarify?
Perhaps the large amount of commits could be due to have we handle the Git repository?
@3keyroman Assuming f556d526df9663c7c2434c2c536aa24eb442c036 is the only relevant commit for this PR?, then there are still a number of whitespace and formatting changes that would be good to leave out to make it easier to review and to discuss further.
@netmackan my last commit resolving the whitespaces and formatting was https://github.com/Keyfactor/signserver-ce/pull/76/commits/a5696d3bf1694e8cd279e5d9b266b09ee58f9027. I am not able to do merge or rebase because of the same conflicts with the html files.
@3keyroman Ok, thanks I see it now. This is likely an issue with our repo. I think I need to create a new PR and just add your commit(s).