feat(integration): add dnsfilter support #5044
Conversation
![propel-code-bot[bot]](https://avatars.githubusercontent.com/in/1179004?s=60&v=4){kind=small}
| | Pre-configured rate-limit handling | ✅ | | ||
| | Per-customer configurations | ✅ | | ||
| </Accordion> | ||
| </AccordionGroup> |
There was a problem hiding this comment.
[Documentation]
Formatting: add a trailing newline at the end of the file.
Context for Agents
[**Documentation**]
Formatting: add a trailing newline at the end of the file.
File: docs/snippets/generated/pennylane/PreBuiltTooling.mdx
Line: 41
hassan254-prog
left a comment
hassan254-prog
left a comment
There was a problem hiding this comment.
This looks good. You forgot to include the main docs page and to add the link to docs.json. You can follow the example on affinity to generate the main docs.
| apiKey: | ||
| type: string | ||
| title: API Key | ||
| description: The API key for your DNSFilter account |
There was a problem hiding this comment.
would be nice to include a pattern, example and doc_section here.
| auth_mode: API_KEY | ||
| proxy: | ||
| base_url: https://api.dnsfilter.com | ||
| docs: https://nango.dev/docs/integrations/all/dnsfilter |
There was a problem hiding this comment.
you left the docs_connect property.
| #### Step 1: Navigate to API Keys Settings | ||
|
|
||
| 1. Log in to your DNSFilter account. | ||
| 2. Click on **Account** in the left sidebar, then select **Account Settings**. | ||
|
|
||
| <img src="/integrations/all/dnsfilter/navigation.png"/> | ||
|
|
||
| 3. Navigate to the **Security** section and scroll down to **API Keys**. | ||
|
|
||
| <img src="/integrations/all/dnsfilter/api_keys.png"/> | ||
|
|
||
| #### Step 2: Create a New API Key |
There was a problem hiding this comment.
maybe these 2 could be combined into a single step (#step-1-generate-an-api-key).
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | JSON Web Token | 6cca780 | packages/providers/providers.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
2 participants
Adds support for dnsfilter platform
Introduce first-party DNSFilter integration (catalog entry, docs & assets)
This PR adds official support for the DNSFilter Platform. All changes are static—covering provider catalog metadata, branding assets, documentation, and auto-generated code snippets—so no runtime or build logic is touched. The goal is to surface DNSFilter in the UI/CLI picker and documentation so customers can quickly discover and connect the service without additional engineering work.
Add DNSFilter First-Party Integration (Catalog Entry, Docs & Branding Assets)
This PR introduces out-of-the-box support for the DNSFilter security platform by adding a provider catalog entry, branded SVG logo, and comprehensive connection documentation. The change set is entirely static—there are no alterations to runtime code, build scripts, or SDKs—so risk is limited to UI/UX presentation and documentation accuracy. Business-wise, the update broadens the integration marketplace, enabling customers to find and configure DNSFilter faster while strengthening the platform’s security story.
Key Changes
• Added DNSFilter provider block to packages/providers/providers.yaml so it surfaces in UI & CLI pickers
• Committed dnsfilter.svg to template-logos for proper branding in light/dark themes
• Auth & usage guide created at docs/integrations/all/dnsfilter/connect.mdx plus autogenerated snippets
• package.json / package-lock.json version bumps produced by docs tooling (no new dependencies)
Affected Areas
• Provider catalog (YAML)
• Documentation site (MDX)
• Branding assets (SVG)
• Generated lockfiles
This summary was automatically generated by @propel-code-bot