cloudfoundry
Feature: add logging rate limits and quotas
What's the user value of this feature request? When logging rate limits and quotas are implemented in CAPI, users should be able to set and get them using the cf CLI.
There are two main parts to this desired change:
- (non-breaking) Add new flags to existing commands in order to create and edit logging rate limits and quotas.
- (breaking) Change table output of certain commands to include logging rate limits and quotas.
Who is the functionality for? Any users interested in setting logging quotas in orgs and spaces (i.e. Org Managers, etc.), or in keeping their apps inside of those same quotas (i.e. Space Developers).
How often will this functionality be used by the user? The updated functionality in the quota commands will be used only occasionally: when a new org/space is created, or an old org/space is desired to be updated to have a new logging quota.
However, it is anticipated that the new logging rate limit flags and table columns will be used very frequently by users who push and manage apps.
Who else is affected by the change? There could be considered a breaking change in the table displays, as new columns could conceivably break users' custom parsing tools for cf CLI table output. Though this can be mitigated by adding the new columns last in the table.
Any users who do not want to set logging quotas in their orgs/spaces need not concern themselves with these changes.
Is your feature request related to a problem? Please describe. There are a number of problems that this feature is trying to solve. See the proposal doc linked below for that list.
This feature request, specifically, is related to the problem of how to make the CAPI changes more idiomatically accessible to new and existing cloudfoundry users.
Describe the solution you'd like TBD
Describe alternatives you've considered N/A
Additional context
- Proposal doc
- https://github.com/cloudfoundry/capi-release/issues/245
