Hi,
Ok, I discovered what it is, although the error message provides no clue at all. There are pipelines using this notebook and the pipeline creates a dependency link which generates the error.
So, instead of deleting the notebook to import again, so I could change the ownership and update the notebook version, I need to follow this sequence:
- Import the new version with a new name
- Change the pipeline to use the new version
- Delete the old version
- Import again, using the old version name
- Change the pipeline to use the old version name
- Delete the notebook with the new name
Important:
- This list is considering only one pipeline. If you have many pipelines using the notebook, consider the additional work
- Deployment pipelines don't work unless you are the owner of all notebooks. If you have a team working on the notebooks, creating notebooks with different owners, the deployment pipelines get completely stuck, because no one will be able to make the deployment overriding notebooks from different owners.
- There is no way to change notebook ownership
- Deletions from source control also get stuck with the pipeline dependencies and can't complete
- If you managed to have the deployment pipeline working and all notebooks with a single owner, but for some reason you still need to drop a notebook and import again following the steps above, you will lose the rules for the notebook.
Kind Regards,
Dennes
