[BUG] Ignore parameter file when not explicitly defined in config file

[shirasassoon]

Library Version

Latest

Python Version

All

Operating System

Windows

Authentication Method

Other

What is the problem?

When the parameter field in the config file is omitted, if a parameter.yml file is present in the repository directory it will be picked up by fabric-cicd and used during the deployment.

Steps to reproduce

1. Use the config.yml file under sample and update workspace and other fields appropriately
2. Remove the parameter field entirely
3. Execute the debug_local config.py file
4. Notice parameter file validation step and parameterization is applied during deployment (when parameter.yml exists under sample workspace folder)

Expected behavior

When the parameter field is omitted in the config file, parameterization should never be applied. The user must explicitly define the parameter field for parameterization to be used during the deployment.

Actual behavior

If there is a parameter.yml file in the repository directory and the parameter field is removed from config file, the deployment uses the parameter file and applies parameterization.

Is there an ideal solution?

Pass in a kwarg from deploy_with_config to FabricWorkspace that skips parameterization when no parameter file path is defined in the config file.

Additional context, screenshots, logs, error output, etc

No response

[microsoft-github-policy-service]

Thank you for submitting this issue, @shirasassoon.
A member of the Fabric CICD team will review your submission and provide feedback shortly.