Feature/update readme

[manikanta-sadurla]

Description

Please provide a brief description of the changes introduced by this pull request.

Related Issue

• Issue Number: Brief description

Checklist

Please ensure that the following steps are completed before submitting the pull request:

• Code follows the Terraform best practices and style guidelines.
• Changes are appropriately documented, including any necessary updates to README or other documentation files.
• Unit tests have been added or updated to cover the changes introduced by this pull request.
• Changes have been tested locally and verified to work as expected.
• The code has been reviewed to ensure it aligns with the project's goals and standards.
• Dependencies and backward compatibility have been considered and addressed if applicable.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Intermediate change (work in progress)

Testing Instructions

Provide detailed steps or instructions for testing the changes introduced by this pull request.

Screenshots

Include any relevant screenshots or visual aids to help reviewers understand the changes visually, if applicable.

Additional Notes

Add any additional notes or context that might be helpful for reviewers or users testing the changes.

[sonarqubecloud]

SonarQube reviewer guide

Summary: Streamline Trivy security scanning workflow and refresh README documentation with clearer module structure and quickstart examples.

Review Focus: The Trivy workflow changes significantly alter the scanning approach—migrating from self-hosted runners to ubuntu-latest, removing artifact uploads, and switching to SARIF output format with exit-code enforcement. Verify this aligns with your security and CI/CD requirements. Additionally, README restructuring removes detailed getting-started content; ensure this information is captured elsewhere (e.g., docs folder).

Start review at: .github/workflows/trivy.yaml. This is critical as it changes your security scanning infrastructure and pipeline behavior, particularly the runner configuration and failure handling logic.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud