[Snyk] Security upgrade werkzeug from 2.1.2 to 3.0.6

[billmetangmo]

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

moto 3.1.4 requires werkzeug, which is not installed.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal
🦉 Allocation of Resources Without Limits or Throttling

[sweep-ai]

Hey @billmetangmo, here are examples of how you can ask me to improve this pull request:

@Sweep Fix the CI errors.

@Sweep Add unit tests to verify that the application works correctly with Werkzeug 3.0.6, particularly testing for:
1. Directory traversal prevention (since this was one of the vulnerabilities fixed)
2. Resource allocation/rate limiting functionality (since this was another vulnerability fixed)

📖 For more information on how to use Sweep, please read our documentation.

[github-actions]

💰 Infracost report

Monthly estimate generated

_{This comment will be updated when code changes.}

[billmetangmo]

❌ Plan Failed

CI link

Error: "name" cannot be longer than 64 characters: "mtchoun-mouh-snyk-fix-29315e2fc15de45288fdacf45438de1c-trigger_user_scan"
 
   with aws_cloudwatch_event_rule.scheduler,
   on main.tf line 326, in resource "aws_cloudwatch_event_rule" "scheduler":
  326:   name                = (terraform.workspace == "mtchoun-mouh-master") ? "trigger_user_scan" : "${terraform.workspace}-trigger_user_scan"
 

Operation failed: failed running terraform plan (exit 1)