fix: state with overrides

[xavidop]

fix an issue when we fetch the sate with overrides

Summary by CodeRabbit

• New Features

  • Added support for overriding API key and subdomain when fetching state in certain workflows.

• Refactor

  • Improved internal handling of API key and subdomain selection for state fetch operations.

• Chores

  • Updated versions of GitHub Actions used in the release build workflow for improved reliability.

[coderabbitai]

Warning

Rate limit exceeded

@xavidop has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 47 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e7c2957 and 741f2d9.

📒 Files selected for processing (3)

• .github/workflows/release_build.yml (1 hunks)
• pkg/test/runner.go (4 hunks)
• pkg/voiceflow/state.go (2 hunks)

Walkthrough

The changes introduce support for API key and subdomain overrides when fetching state in the test runner. Function signatures in the test runner and state fetcher are updated to accept and propagate these overrides, and a new function handles the state fetching logic with optional override parameters. GitHub Actions workflow dependencies are also updated.

Changes

File(s)	Change Summary
.github/workflows/release_build.yml	Updated versions of sigstore/cosign-installer (v3.9.0 → v3.9.1) and anchore/sbom-action/download-syft (v0.20.1 → v0.20.2).
pkg/test/runner.go	Propagated apiKeyOverride and subdomainOverride through function signatures and calls; updated state fetch call to use overrides.
pkg/voiceflow/state.go	Refactored FetchState to delegate to new FetchStateWithOverrides, which supports API key and subdomain overrides. Added new function.

Sequence Diagram(s)

sequenceDiagram
    participant TestRunner
    participant Validator
    participant Checker
    participant VoiceflowState

    TestRunner->>Validator: validateResponse(..., apiKeyOverride, subdomainOverride)
    Validator->>Checker: checkVariableValue(..., apiKeyOverride, subdomainOverride)
    Checker->>VoiceflowState: FetchStateWithOverrides(..., apiKeyOverride, subdomainOverride)
    VoiceflowState-->>Checker: state/err
    Checker-->>Validator: validationResult
    Validator-->>TestRunner: validationResults

Loading

Poem

A bunny hopped through fields of code,
With keys and domains in override mode.
Functions extended, signatures grew,
State fetched with options shiny and new.
Actions updated, dependencies tight—
The garden of code feels just right! 🥕

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch xavier/fix-fetch-state-overrides

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 auto-generate unit tests to generate unit tests for 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.