[BUG] Reports with accented characters fail parameter replacement in v0.34

[philippedurocher]

Library Version

0.1.34

Python Version

3.12.11

Operating System

Windows

Authentication Method

Azure CLI (az login)

What is the problem?

Hello. I'm currently updating from version .30 to version .34 and I'm getting errors with reports that contain accented characters in their names.

Here's an example:

I didn't have these errors with version .30

The report exists in my folder, it is deployed and the transformations are applied.

Thank you.

Steps to reproduce

Create a report with accented characters and try do deploy using fabric-cicd 0.1.34

Expected behavior

fabric-cicd should not display an error due to a not found report
The transformations should be applied to the report files before deploying

Actual behavior

fabric-cicd reports the report as not found and does not apply the transformations as specified in the parameter.yml file.

Is there an ideal solution?

Probably to make fabric-cicd accent sensitive so it should be able to find report names with accented characters.

Additional context, screenshots, logs, error output, etc

The log
debug.log

The deployment config file
gold_dsn.config.yml

Parameter.yml file
parameter.yml

My deploy script file (basically a call to deploy_with_config() with some arguments)
deploy_ws.py

[shirasassoon]

/triaged

@philippedurocher Thanks for raising this issue. Can you please provide the parameter input, the error gets thrown when the item_name file filter is present, I would like to better understand the error.

[shirasassoon]

/needinfo

[philippedurocher]

@shirasassoon Thank your for your response.

I added the log, config, parameter.yml and my deploy script in the bug description. I hope this helps.

I also edited the description : the report is deployed and the transformations are applied. It's just an error and a warning about the file not being found in the directory, but it gets deployed/transformed. So it's quite minor.

Thank you.

[shirasassoon]

/triaged

@philippedurocher Thanks for the additional information! I will look into it further.

[microsoft-github-policy-service]

Triage has been completed for this issue.