Bugfix/350 Fix ConfigParser Error for New Teams Workflow URL (#350)

[MarcelMWS]

Requirements

• Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
• All new code requires tests to ensure against regressions
• Remember to set idealista:develop as base branch;

Description of the Change

• Issue Addressed: Fixes configparser error related to new Teams URL/workflow (see comment: Issue #350):

  • configparser.InterpolationSyntaxError: '%' must be followed by '%' or '(', found: '%2Ftriggers%2Fmanual%2Frun&sv=1.0&s'

• Enhancement: You can now insert Teams workflow URLs without needing to escape the % character.

Benefits

• Dependency Upgrade: Updated dependencies to address all vulnerabilities and CVEs in the image.

Possible Drawbacks

Applicable Issues

I intended to check out the develop branch but mistakenly checked out version 5.0.0 instead. I ended up reverting two commits, effectively returning to a state similar to the develop branch. I’ll be sure to double-check my branch next time.

Tests

• Running Tests...
• Test 1: OK
• Test 2: OK
• Test 3: OK
• Destroying Containers...
• TESTS FINISHED SUCCESSFULLY

[angelosnm]

LGTM

[sebagarayco]

Hitting this issue. Is this going to be merged soon?

[Cute-Monster]

Hitting this issue. Is this going to be merged soon?

Hi @sebagarayco,
As workaround you can replace %2F with actual human-readable value / 😺
This helped me to avoid this issue while migrating to new MS Teams workflow flow

[sebagarayco]

Hitting this issue. Is this going to be merged soon?

Hi @sebagarayco, As workaround you can replace %2F with actual human-readable value / 😺 This helped me to avoid this issue while migrating to new MS Teams workflow flow

You rock, that did it. Appreciate it!

[angelosnm]

Guys...it is just one click away...