Publisher Command Center: Allow publishers to publish #135
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonkeane
approved these changes
May 20, 2025
Collaborator
jonkeane
left a comment
jonkeane
left a comment
There was a problem hiding this comment.
I'm fine to remove this for now — it would be nice to display this information if we could get to it — are there already issue(s) for exposing that (probably at least one in Connect itself?)
Collaborator
Author
|
I'll file one |
tdstein
approved these changes
May 20, 2025
Contributor
tdstein
left a comment
tdstein
left a comment
There was a problem hiding this comment.
Agreed. It would be awesome to expose these types of metrics to publishers so they can understand application performance.
Collaborator
Author
|
Issue created: https://github.com/posit-dev/connect/issues/31544 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #127
The Publisher Command Center could not be published by a Publisher because it called the unversioned, admin-only
metrics/procsendpoint. It used this to display CPU and memory usage for processes.I removed those calls and removed their display from the UI, so now the content will run successfully with a Publisher API key.
I deployed the content to my local dev Connect environment and confirmed that it could run from a Publisher account, kill processes, etc.
I bumped the version so that it releases to the gallery. @fizzboop this might affect your open PR on the same piece of content — we can coordinate on that if we need to!
Screenshots attached showing before and after: