Skip to content

[Components] zoom_admin - fix to get-meeting-recordings #16940

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jocarino
Copy link

@jocarino jocarino commented Jun 3, 2025

WHY

Correct downloadAccessToken -> string not a boolean
Add TTL for the token
Removed pagination on recordings -> wrong prop and don't need this or won't show other important props
Tested custom version on workflow to check it's working as intended
Screenshot 2025-06-03 at 11 36 11

Summary by CodeRabbit

  • New Features

    • Added an optional setting to specify how long the download access token for meeting recordings remains valid (up to 7 days).
  • Refactor

    • Improved how meeting recording downloads are handled for greater flexibility and control.

Copy link

vercel bot commented Jun 3, 2025

Someone is attempting to deploy a commit to the Pipedreamers Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

vercel bot commented Jun 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jun 4, 2025 5:56pm

Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

Walkthrough

The code updates the Zoom Admin "get-meeting-recordings" action by adding an optional ttl property to control download access token lifespan, removes the old download_access_token flag, and refactors the run method to call listMeetingRecordings directly with updated parameters. The action version is incremented.

Changes

File(s) Change Summary
components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs Added optional ttl property, removed download_access_token flag, refactored run method, bumped version to 0.0.2

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Action
    participant ZoomAdmin

    User->>Action: Invoke get-meeting-recordings (with optional ttl)
    Action->>ZoomAdmin: listMeetingRecordings({ include_fields, ttl })
    ZoomAdmin-->>Action: Return meeting recordings (with optional download token)
    Action-->>User: Return recordings data
Loading

Poem

🐰
Hopping through code, a new field appears,
"TTL" for tokens, to last days or years.
The old flag is gone, the method’s refined,
Now cleaner, more nimble, with logic aligned.
Version hops up, the action’s brand new—
A rabbit’s salute to this code review!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d6802e and 379e23d.

📒 Files selected for processing (1)
  • components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@adolfo-pd adolfo-pd added the User submitted Submitted by a user label Jun 3, 2025
@pipedream-component-development
Copy link
Collaborator

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

@pipedream-component-development
Copy link
Collaborator

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (1)

2-2: Remove unused import.

The paginate import is no longer used after the refactoring that removes pagination in favor of direct API calls.

-import { paginate } from "../../common/pagination.mjs";
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 56a1a2e and 3d6802e.

📒 Files selected for processing (1)
  • components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (2 hunks)
🔇 Additional comments (3)
components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (3)

10-10: LGTM!

Appropriate version bump for the changes made.


26-33: LGTM!

The TTL property is well-defined with appropriate constraints and clear documentation. The 7-day maximum aligns with typical token expiration practices.


36-45:

❓ Verification inconclusive

Verify API parameter requirements.

The parameter building logic is well-structured and correctly implements the conditional inclusion of include_fields and ttl. The refactoring from pagination to direct API calls aligns with the PR objectives.

Please verify that the Zoom API supports the ttl parameter when include_fields=download_access_token is used:


🏁 Script executed:

#!/bin/bash
# Search for API documentation or usage examples of the ttl parameter with Zoom recordings API
rg -i "ttl.*download.*token|download.*token.*ttl" --type js
rg -i "listMeetingRecordings.*ttl|ttl.*listMeetingRecordings" --type js

Length of output: 135


Verify TTL parameter support in Zoom API.

The refactored logic correctly adds include_fields = "download_access_token" and ttl only when downloadAccessToken is enabled. We didn’t find any in-repo examples of TTL usage—please confirm that Zoom’s Cloud Recording API supports a ttl parameter on the listMeetingRecordings endpoint when include_fields=download_access_token (see https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/recordingget).

@jocarino jocarino changed the title Fix - Remove paginate and update parameters [Components] zoom_admin - fix to get-meeting-recordings Jun 4, 2025
Copy link
Collaborator

@GTFalcao GTFalcao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jocarino , thanks for your contribution!

The package.json needs to have its version updated as well for this change to be published. I'll move this forward so it can be QA'd.

@GTFalcao GTFalcao moved this from Ready for PR Review to Ready for QA in Component (Source and Action) Backlog Jun 11, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to Ready for Release in Component (Source and Action) Backlog Jun 12, 2025
@vunguyenhung
Copy link
Collaborator

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Components-zoom_admin-fix-to-get-meeting-recordings-20fbf548bb5e8142a286c82bdf179bd7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User submitted Submitted by a user
Projects
Status: Ready for Release
Development

Successfully merging this pull request may close these issues.

5 participants