fix: aws-cloud-regression-suite.yml

[venkatamutyala]

PR Type

configuration changes

---

Description

• Added a workflow_dispatch trigger to the AWS Regression Suite workflow to enable manual execution of the workflow.
• Corrected the placement of the workflow_dispatch trigger by removing it from under the concurrency section.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	aws-cloud-regression-suite.yml Add manual trigger and fix workflow configuration                .github/workflows/aws-cloud-regression-suite.yml Added workflow_dispatch trigger to allow manual workflow runs. Removed misplaced workflow_dispatch under concurrency. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[sonarqubecloud]

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 SonarCloud

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Workflow Trigger Verify that adding the workflow_dispatch trigger doesn't interfere with the existing pull_request trigger and that both triggers function as intended.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Add customizable inputs for manual workflow triggers to increase flexibility Consider adding environment variables or inputs for the workflow_dispatch event to allow customization when manually triggering the workflow. .github/workflows/aws-cloud-regression-suite.yml [3-6] on: pull_request: types: [opened, synchronize, reopened] workflow_dispatch: + inputs: + environment: + description: 'Environment to run tests against' + required: true + default: 'staging' Apply this suggestion Suggestion importance[1-10]: 8 Why: Introducing inputs for the workflow_dispatch event enhances flexibility by allowing users to customize the workflow when triggered manually. This is a valuable improvement, increasing the utility of the manual trigger.	8
	Specify target branches for the pull request trigger to optimize workflow execution Consider adding a branches filter to the pull_request trigger to specify which branches should trigger the workflow. This can help reduce unnecessary workflow runs. .github/workflows/aws-cloud-regression-suite.yml [3-6] on: pull_request: types: [opened, synchronize, reopened] + branches: [main, develop] workflow_dispatch: Apply this suggestion Suggestion importance[1-10]: 7 Why: Adding a branches filter to the pull_request trigger can help optimize workflow execution by reducing unnecessary runs. This suggestion is relevant and can improve the efficiency of the workflow.	7

💡 Need additional feedback ? start a PR chat