[A2ELAOUDI]

Related Issues

• fixes Enforce Ruff docstring rules #2947

Proposed Changes:

Enables the docstring rules from #2947 (D102, D103, D205, D209, D213, D417, D419) in the last five integrations that did not have them yet, following the same pattern as #3008–#3012:

• amazon_sagemaker: rules enabled, D added to the tests per-file-ignores (matching the other integrations), one D205 fix.
• arcadedb: rules enabled, seven D205 fixes in document_store.py (blank line after the summary; one two-line summary condensed to a single line, and a missing period added).
• azure_doc_intelligence, azure_form_recognizer: rules enabled, no violations.
• litellm: rules enabled, five D213 fixes (summary moved to the second line).

The new-integration template (scripts/utils/templates/pyproject.toml) already enables these rules. With this PR, all integrations under integrations/ do too.

How did you test it?

• ruff check . and ruff format --check . pass in each of the five integrations.
• hatch run test:unit passes for amazon_sagemaker (12 passed), arcadedb (137 passed) and litellm (28 passed). The azure integrations only had pyproject changes.

Notes for the reviewer

Only docstrings and ruff config changed. There are no code changes.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Heads-up for maintainers

This PR is from a fork and touches integrations whose integration tests require API keys.
Those tests are skipped in CI because fork PRs don't have access to repo secrets for security reasons.

Affected integrations:

• arcadedb
• azure_doc_intelligence
• azure_form_recognizer
• litellm

Please run the integration tests locally (hatch run test:integration inside each folder) before approving.

[github-actions]

Coverage report (arcadedb)

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
integrations/arcadedb/src/haystack_integrations/document_stores/arcadedb
document_store.py
Project Total

This report was generated by python-coverage-comment-action

[github-actions]

Coverage report (litellm)

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
integrations/litellm/src/haystack_integrations/components/generators/litellm/chat
chat_generator.py
Project Total

This report was generated by python-coverage-comment-action

[github-actions]

Coverage report (amazon_sagemaker)

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
integrations/amazon_sagemaker/src/haystack_integrations/components/generators/amazon_sagemaker
sagemaker.py
Project Total

This report was generated by python-coverage-comment-action

[github-actions]

Coverage report (azure_doc_intelligence)

This PR does not seem to contain any modification to coverable code.

[github-actions]

Coverage report (azure_form_recognizer)

This PR does not seem to contain any modification to coverable code.

[HaystackBot]

Hi @A2ELAOUDI, thanks a lot for your contribution! 🙏

We noticed that the Contributor License Agreement (CLA) check (license/cla) hasn't passed yet, so we've temporarily moved this PR to draft and paused the review assignment.

To get your PR reviewed, please sign the CLA via the link in the license/cla check below (or in the CLA bot comment). As soon as the check turns green, this PR will automatically be marked ready for review again and a reviewer will be re-assigned.

[HaystackBot]

Thanks for signing the CLA, @A2ELAOUDI! 🎉 This PR is now ready for review again and the reviewer has been re-assigned.

[julian-risch]

Thank you @A2ELAOUDI !