-
Notifications
You must be signed in to change notification settings - Fork 156
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
[ShopifyVM] Dev Dash - app logs #5490
Closed
Closed
Conversation
This file contains 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
6502b14
to
dbd1ed9
Compare
Coverage report
Test suite run success2112 tests passing in 930 suites. Report generated by 🧪jest coverage report action from 421666b |
We detected some changes at packages/*/src and there are no updates in the .changeset. |
421666b
to
d55416e
Compare
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.
Part of: https://github.com/Shopify/shopify-functions/issues/605
Note:
We will need the relevant Core and Partners PR to be merged and do not have them merged. Hoping to get review on the approach I've taken, specically around how we fetch the app logs.
For polling app logs, in
dev
andlogs
, I've added this to determine which client to use.Another option or alternative, is we can move the
fetchAppLogs
to theDeveloperPlatformClient
, but think this would involved a larger refactor and would prefer to tackle in another PR or issue.WHY are these changes introduced?
This PR is for integrating app logs polling with the developer dashboard.
Background:
There is 2 steps for polling:
Subscribe - This is done through the
DeveloperPlatformClient
organizationId: string
, we also needappId
for the request, we alraedy have access to that through the cli contextFetch App Logs - is a bit more complicated since we dont use the
DeveloperPlatformClient
dev
andlogs
pollAppLogs
in the CLI, there is no concept of what client is being used (to know whether to make request to partners or app management)fetchAppLogsDevDashboard
WHAT is this pull request doing?
Update the
subscribeToAppLogs
for theapp-management-client
to make request to new core endpoint (which will proxy request to partners for now) Endpoint on this branch.js.add-app-log-endpoints-2
appId
, andorgId
for app management requests, which are now passed inUpdate polling app logs for
dev
andlogs
organizationSource
to know which endpoint to make request toHow to test your changes?
Will need:
🎩
Post-release steps
Measuring impact
How do we know this change was effective? Please choose one:
Checklist