Constraint changes should be auditable

[szczygiel-m]

We would like the form for adding constraints to include an additional text field “reason” whose purpose would be to hold a description of why the constraint was added.

[adriansobolewski]

Does "constraints" refer to Workload constraints management?

[szczygiel-m]

Does "constraints" refer to Workload constraints management?

Hi, actually it refers to topic/subscription constraint which is set usually by hermes admin to add more consumers and processing power for lagging subscription. This is the endpoint for this feature 😄

[adriansobolewski]

I'd like to work on this task then :)

I also have some clarifying questions:

1. Should the new reason field be required and not blank?
2. Do you have in mind some upper bound for the text length? Does 512 characters sound reasonable? :)
3. Is this endpoint also used by some GUI layer and frontend needs to be adjusted as well?

[szczygiel-m]

Great to hear that :)

1. hmm, I think It will be ok if this field would not be required, we wouldn't want to break any external users integration with this feature.
2. No, but 512 chars seems ok, i think that we can go even for 1024 chars :)
3. Yes, it is used by gui, You can check it out by running hermes-console as described in readme, and then go to admin tools -> constraints
   
   In case of any problems or further questions - feel free to ask :)