Adding custom representer for yaml.dump to ensure that string values are enclosed in the quotation marks.
Related Issue
106
Motivation and Context
If any string value in the generated bundle.yaml can be interpretted as something other than a string, e.g. number in scientific notation, deployment to Databricks may / will fail. It definitly guarantees failed deployment when this case occurs for policy_id for cluster.
How Has This Been Tested?
I've used local installation of brickflow with this change to generate the updated bundle and successfully deployed it Databricks. Workflow was successfully created with the correct cluster setup and any other expected configuration.
Screenshots (if appropriate):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Closes #106
Description
Adding custom representer for yaml.dump to ensure that string values are enclosed in the quotation marks.
Related Issue
106
Motivation and Context
If any string value in the generated
bundle.yamlcan be interpretted as something other than a string, e.g. number in scientific notation, deployment to Databricks may / will fail. It definitly guarantees failed deployment when this case occurs forpolicy_idfor cluster.How Has This Been Tested?
I've used local installation of brickflow with this change to generate the updated bundle and successfully deployed it Databricks. Workflow was successfully created with the correct cluster setup and any other expected configuration.
Screenshots (if appropriate):
Types of changes
Checklist: