Skip to content
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

[ENH]: Add support for processing the enhanced guardrail scanning feature in shield module #163

Open
1 task done
akhil31415 opened this issue Dec 19, 2024 · 0 comments
Open
1 task done
Assignees
Labels
enhancement New feature or request

Comments

@akhil31415
Copy link
Contributor

Contact Details

No response

Feature Description

The Shield module must support the new guardrail feature, enabling content policy scans using multiple providers.

Acceptance Criteria

Configuration Processing:

The Shield must accept and process guardrail configurations provided alongside the message.
The system should validate the guardrail configuration and return an error for invalid or unsupported configurations.

Provider Support:

The Shield should support multiple content policy providers and apply the appropriate scanning logic based on the configuration.
If a provider is not specified, the default provider should be used for scanning.

Message Scanning:

The Shield must scan the message according to the policies defined in the guardrail configuration.
The scan should be executed within a specified response time (e.g., X milliseconds).

Tag Extraction:

Relevant tags must be accurately extracted from the message based on the scan results.
The extracted tags should match the structure and format defined by the guardrail configuration.

Error Handling:

If a scan cannot be completed (e.g., due to missing or invalid configurations), an appropriate error message must be returned.
Logs should be generated for all scan failures to assist with debugging.

Performance:

The system should handle concurrent scanning requests without degradation in performance.
The Shield must meet performance benchmarks under load testing conditions (e.g., X scans per second).

Testing:

Unit tests should cover all scenarios, including valid scans, invalid configurations, and multiple providers.
Integration tests should validate end-to-end functionality with different content policy providers.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@akhil31415 akhil31415 added the enhancement New feature or request label Dec 19, 2024
@akhil31415 akhil31415 changed the title [ENH]: Add support for processing the enhanced guardrail scanning feature [ENH]: Add support for processing the enhanced guardrail scanning feature in shield module Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant