[FEAT] fabric_notebook support for .py file as definition source

[arildandas]

🚀 Feature description

As fabric notebook content is integrated with git as notebook-content.py files, it is very inconvenient that the only supported file format for definition source is .ipynb. One of the main uecases for this terraform resource is to deploy it from a git branch to the next environment, ie. Test or Prod.
To make this process more seemless with this terraform resource it would be extremly useful if one could point directly to the .py file. like this example:

resource "fabric_notebook" "example_definition_update" {
  display_name = "example"
  description  = "example with definition update when source or tokens changed"
  workspace_id = "00000000-0000-0000-0000-000000000000"
  definition = {
    "notebook-content.py" = {
      source = "${local.path}/notebook-content.py"
      tokens = {
        "MESSAGE" = "World"
        "MyValue" = "Lorem Ipsum"
      }
    }
  }
} 

🔈 Motivation

The deployment process using terraform resource for notebooks based on git source would be much more seemless and straight forward to use.

🛰 Alternatives

Alternative deployment with Fabric REST API can be used, but is more cumbersome:
REST API doc: https://learn.microsoft.com/en-us/rest/api/fabric/notebook/items/update-notebook-definition?tabs=HTTP

Example API usage with .py source:

POST https://api.fabric.microsoft.com/v1/workspaces/cfafbeb1-8037-4d0c-896e-a46fb27ff229/notebooks/5b218778-e7a5-4d73-8187-f10824047715/updateDefinition?updateMetadata=True

{
  "definition": {
    "parts": [
      {
        "path": "notebook-content.py",
        "payload": "IyBGYWJyaWMgbm90ZWJv...",
        "payloadType": "InlineBase64"
      },
      {
        "path": ".platform",
        "payload": "ZG90UGxhdGZvcm1CYXNlNjRTdHJpbmc=",
        "payloadType": "InlineBase64"
      }
    ]
  }
}

🚧 Potential Configuration / Desired Solution

resource "fabric_notebook" "example_definition_update" {
  display_name = "example"
  description  = "example with definition update when source or tokens changed"
  workspace_id = "00000000-0000-0000-0000-000000000000"
  definition = {
    "notebook-content.py" = {
      source = "${local.path}/notebook-content.py"
      tokens = {
        "MESSAGE" = "World"
        "MyValue" = "Lorem Ipsum"
      }
    }
  }
}

📎 Additional context

No response

☑️ Acceptance Criteria

The fabric_notebook resource can be used with notebook-content.py source as integrated with fabric git as the sample config described Potential Configuration above

🔰 Code of Conduct

• I agree to follow this project's Code of Conduct.

[DariuszPorowski]

Hi @arildandas Thank you for the feature request. It's a valid idea. Will bring this to the design discussion with the team (most likely after the holiday season).