llama-stack-mirror/docs/source/providers/safety
Sumanth Kamenani 0b00c68d59
fix: use lambda pattern for bedrock config env vars (#3307)
# What does this PR do?

Improved bedrock provider config to read from environment variables like
AWS_ACCESS_KEY_ID. Updated all
fields to use default_factory with lambda patterns like the nvidia
provider does.

  Now the environment variables work as documented.

  Closes #3305

  ## Test Plan

  Ran the new bedrock config tests:
  ```bash
python -m pytest tests/unit/providers/inference/bedrock/test_config.py
-v

Verified existing provider tests still work:
  python -m pytest tests/unit/providers/test_configs.py -v
2025-09-05 10:45:11 +02:00
..
index.md chore(misc): make tests and starter faster (#3042) 2025-08-05 14:55:05 -07:00
inline_code-scanner.md docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
inline_llama-guard.md docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
inline_prompt-guard.md docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
remote_bedrock.md fix: use lambda pattern for bedrock config env vars (#3307) 2025-09-05 10:45:11 +02:00
remote_nvidia.md docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
remote_sambanova.md feat(starter)!: simplify starter distro; litellm model registry changes (#2916) 2025-07-25 15:02:04 -07:00