Mend - fix werkzeug issue Part1

[AndreKurait]

Description

We are currently getting a mend issue for werkzeug even though we’ve updated it.
Experimentation showed that deleting the requirements.txt refreshes the mend check.

This should be merged, and after mend runs, #639 should be merged.

• Category: Maintenance
• Why these changes are required? Refresh Mend check
• What is the old behavior before changes and new behavior after changes? Mend shows up failing for werkzeug

Issues Resolved

MIGRATIONS-1728

Is this a backport? If so, please add backport PR # and/or commits #

Testing

Branch testing for mend fix, commit will be reverted

Check List

• [ x] New functionality includes testing
  • [x ] All tests pass, including unit test, integration test and doctest
• [x ] New functionality has been documented
• [x ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[peternied]

@AndreKurait Can you see about running mend on your fork to confirm that its working rather than trial an erroring in the shared repo? Just occurred to me, did you manage to reachout to the maintainers of opensearch-py about issues like this?

Finally, if we don't have any better ideas about how to properly trigger and test the mend workflow, what would you think about filing a ticket with support?

[AndreKurait]

@AndreKurait Can you see about running mend on your fork to confirm that its working rather than trial an erroring in the shared repo? Just occurred to me, did you manage to reachout to the maintainers of opensearch-py about issues like this?

Finally, if we don't have any better ideas about how to properly trigger and test the mend workflow, what would you think about filing a ticket with support?

I tested on a branch on this repo. I tried changing settings such as incremental scan or other whitesource settings. The only change that fixed the issue was deleting both dev-requirements.txt and requirements.txt

I just sent a support email to mend to see if they can fix the issue without going through this process