Activity log for bug #1790954
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2018-09-05 20:14:34 | Lance Bragstad | bug | added bug | ||
2018-09-05 20:14:47 | Lance Bragstad | description | Currently, the Enforcer objects can be instantiated with optional callbacks, although it doesn't really make sense to never supply a callback. If the purpose of oslo.limit is to calculate usage and enforce it against a limit, the callback will always be required. We should remove this as an optional parameter. | Currently, the Enforcer objects can be instantiated with optional callbacks [0], although it doesn't really make sense to never supply a callback. If the purpose of oslo.limit is to calculate usage and enforce it against a limit, the callback will always be required. We should remove this as an optional parameter. [0] https://github.com/openstack/oslo.limit/blob/master/oslo_limit/limit.py#L56 | |
2018-09-06 17:47:15 | Lance Bragstad | summary | Make callbacks a required for enforcement | Make callbacks required for enforcement | |
2018-09-06 17:47:33 | Lance Bragstad | oslo.limit: status | New | Triaged | |
2018-09-06 17:47:36 | Lance Bragstad | oslo.limit: importance | Undecided | Medium | |
2018-09-20 00:50:41 | Vishakha Agarwal | oslo.limit: assignee | Vishakha Agarwal (vishakha.agarwal) | ||
2018-09-24 14:15:07 | OpenStack Infra | oslo.limit: status | Triaged | In Progress | |
2022-03-15 01:26:52 | melanie witt | oslo.limit: status | In Progress | Fix Released | |
2022-03-15 01:26:52 | melanie witt | oslo.limit: assignee | Vishakha Agarwal (vishakha.agarwal) |