-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Add missing payload_template config option in Scrape #39329
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
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughA new configuration option, Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant ScrapeIntegration
User->>ScrapeIntegration: Configure with payload_template
ScrapeIntegration->>ScrapeIntegration: Render template for POST payload
ScrapeIntegration->>ScrapeIntegration: Send POST request with rendered payload
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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)
source/_integrations/scrape.markdown (1)
63-66
: Enhance docs with a concrete usage example.Consider adding an example in the “Container cleaning by CleanProfs” section (or a new snippet) to illustrate how
payload_template
can substitute variables at runtime. For instance:--- a/source/_integrations/scrape.markdown +++ b/source/_integrations/scrape.markdown @@ 277,283 - method: POST - payload: zipcode=5624JW&street_number=17 + method: POST + # Using payload_template to inject dynamic values + payload_template: "zipcode={{ zipcode }}&street_number={{ street_number }}" headers: Content-Type: application/x-www-form-urlencoded
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
source/_integrations/scrape.markdown
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - home-assistant-docs
- GitHub Check: Header rules - home-assistant-docs
- GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (1)
source/_integrations/scrape.markdown (1)
63-66
: Correctly document thepayload_template
option.The new
payload_template
entry mirrors the existingpayload
field but adds template support, with the correcttype: template
and optional status. This aligns with other template-based configuration options in this file.
Proposed change
SSIA
#38747
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit
payload_template
option for the scrape integration, enabling users to specify a POST request payload with template support.