[PR #2857] feat: Allow users to specify AWS Bedrock validation models #23875

Closed
opened 2026-02-21 20:21:55 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langgenius/dify/pull/2857

State: closed
Merged: Yes


Description

The model currently used for AWS Bedrock verification is Hardcode. If users are supported to specify names through environment variables, the user experience will be better.

AWS_BEDROCK_VALIDATE_MODEL='amazon.titan-text-lite-v1'

allow model type:

api/core/model_runtime/model_providers/bedrock/llm/_position.yaml

rel issue: #2856, #2829

Type of Change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update, included: Dify Document

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • TODO

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
  • optional I have made corresponding changes to the documentation
  • optional I have added tests that prove my fix is effective or that my feature works
  • optional New and existing unit tests pass locally with my changes
**Original Pull Request:** https://github.com/langgenius/dify/pull/2857 **State:** closed **Merged:** Yes --- # Description The model currently used for AWS Bedrock verification is Hardcode. If users are supported to specify names through environment variables, the user experience will be better. ```bash AWS_BEDROCK_VALIDATE_MODEL='amazon.titan-text-lite-v1' ``` allow model type: ```bash api/core/model_runtime/model_providers/bedrock/llm/_position.yaml ``` rel issue: #2856, #2829 ## Type of Change Please delete options that are not relevant. - [x] New feature (non-breaking change which adds functionality) - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) # How Has This Been Tested? Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration - [ ] TODO # Suggested Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] My changes generate no new warnings - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods - [x] `optional` I have made corresponding changes to the documentation - [x] `optional` I have added tests that prove my fix is effective or that my feature works - [x] `optional` New and existing unit tests pass locally with my changes
yindo added the pull-request label 2026-02-21 20:21:55 -05:00
yindo closed this issue 2026-02-21 20:21:56 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#23875