Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1593
@rhtyd @jburwell @rafaelweingartner Can we use event_details table which
is not used at the moment? if we consider sanity job to generate event_id=0
then max_id can be easily represented there as ("id","0","max_id","value")
Alternatively a new table would require new DAO isn't it? Seems to be huge
scope creep for such a minor fix as permission issue. Can we just merge it as
it is and open another PR for the extended scope?
Advertising
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
