You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there functionality to modify the default_lakehouse found in the #METADATA section of the notebook definition?
# METADATA ********************
# META {
# META "kernel_info": {
# META "name": "synapse_pyspark"
# META },
# META "dependencies": {
# META "lakehouse": {
# META "default_lakehouse": "8da5e04c-2ecc-47e3-ab45-9dc7e8adb69b",
# META "default_lakehouse_name": "lh_config",
# META "default_lakehouse_workspace_id": "7157d32b-5d50-4125-bb55-8c60f27cccbd"
# META }
# META }
# META }
### Additional context
No response
The text was updated successfully, but these errors were encountered:
@richbenmintz Thank you for your question, the answer is yes! Please check out parameterization. You can leverage parameterization to find and replace specified strings found in the repository files, such as the default_lakehouse connection string, default_lakehouse_name, etc. Please take a look at our documentation on parameterization for additional guidance and a relevant example: https://microsoft.github.io/fabric-cicd/latest/how_to/parameterization/
Also, we are in the process of refactoring our parameter file structure so please keep an eye out for updated documentation in the near future.
Thanks, I understand that find and replace will replace all instances of a string with the defined replacement value, however I may not want to replace all instances of 'lh_config' with some other value in my file. It would be great to have the ability to define in which files and or types of files that I want to perform the replace functionality. Not sure if a file name includes or a file name excludes makes for sense. but something like: - fileType: notebooks - include: all
What is the question?
Is there functionality to modify the default_lakehouse found in the #METADATA section of the notebook definition?
No response
The text was updated successfully, but these errors were encountered: