Error using --resource-tags option after upgrading Prowler to 4.3.7

[ShivaSDP]

Steps to Reproduce

❯❯ prowler.exe --version
Prowler 4.3.7

❯❯ prowler aws --region ap-south-1 --resource-tags Environment=dev Project=DEV

-> Using the AWS credentials below:
.

There are no findings in Account xxxxxxxxxx

Expected behavior

❯❯ prowler --version
Prowler 4.3.5 (latest is 4.3.7, upgrade for the latest features)

❯❯ prowler aws --region ap-south-1 --resource-tags Environment=dev Project=DEV

-> Using the AWS credentials below:
.

-> Using the following configuration:
.

Executing 383 checks, please wait...

-> Scan completed! |▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉| 383/383 [100%] in 9:42.1

Actual Result with Screenshots or Logs

❯❯ prowler aws --region ap-south-1 --resource-tags Environment=dev Project=DEV

-> Using the AWS credentials below:
.

There are no findings in Account xxxxxxxxxx

How did you install Prowler?

From pip package (pip install prowler)

Environment Resource

1. EC2 Instance (Ubuntu)
2. Windows Laptop

OS used

1. Ubuntu
2. Windows 11

Prowler version

4.3.7

Pip version

23.3.1

Context

No response

[jfagoagas]

Hello @ShivaSDP, we are going to review it and we'll back to you once we have an update on it.

Thanks for using Prowler 🚀

[MrCloudSec]

Hi @ShivaSDP, I could not reproduce your error.

Can you execute it again with --log-level ERROR, please? Thanks!

[ShivaSDP]

I have tested it with below versions -
4.3.5 (working)
4.3.6 (not working)
4.3.7 (not working)
4.4.0 (working)

Below are the screenshots

4.3.6

4.3.7

latest, 4.4.0

[ShivaSDP]

Issue can be closed as it is working fine with the latest version (4.4.0).

[MrCloudSec]

Perfect! Glad that it works now 😄