-
Notifications
You must be signed in to change notification settings - Fork 942
Show routable / readiness state in the cf app
command
#3350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I've built a POC in my fork at feat/add-ready-column. |
I just noticed that the RFC contains an example on how to implement this part:
I deviated a little bit because the wording around this feature is all "ready" / "readiness" and suddenly showing "routable" seems odd to me. I've also placed it after the |
This issue can probably be closed as this PR has been merged: |
I just tested with the latest v8 CLI and the feature is not there, seems like it was only merged to main. @joaopapereira @a-b do you plan to bring this to v8 as well or will it only be v9? |
Uh oh!
There was an error while loading. Please reload this page.
What's the user value of this feature request?
Right now readiness checks can be configured via the manifest but the CLI doesn't give any indication whether an application is ready. This causes confusion as the app is unreachable (404: route not found) but in the CLI it is shown as running with no indication of anything being wrong.
Who is the functionality for?
Users pushing apps with readiness checks.
How often will this functionality be used by the user?
Often, every time the readiness of app instances needs to be inspected.
Who else is affected by the change?
Operators who troubleshoot issues reported by users, anyone who might be parsing the output of the
cf app
command.Is your feature request related to a problem? Please describe.
Yes, it is tedious to use
cf curl
s to find the processes and list their stats to view the routable state.Describe the solution you'd like
An additional column in the process table to view the readiness / routable state:
Describe alternatives you've considered
An additional command but that seems unnecessary for just viewing such information.
Additional context
RFC0020 Readiness Healthchecks
CC v3 API: The process stats object
I'm willing to provide a PR for this.
The text was updated successfully, but these errors were encountered: