Notebook Issue with Environment Deployment between Workspaces

[Anonymous]

I've encountered an issue when deploying from the 'dev' workspace to the 'prod' workspace. Despite creating the same environment, named 'env', in both workspaces, I consistently receive the error message 'The environment you've selected isn't available in this workspace. You can create a new environment in this workspace, then select that environment in the notebook ribbon.' in all notebooks within the 'prod' workspace after deployment.

As a workaround, I manually reset the environment selection in each affected notebook.

Is there a way to automate this process or set it as a rule?

 

 

[uselessai_in]

I noticed something similar and wrote about it - https://uselessai.in/fabrics-weird-comparison-in-deployment-pipelines-b260f68f2fb6

[afraaij_Amphia]

I didn't read everything but this workarround does work for now:

When creating a workspace under:
Workspace settings > Data Engineering / Science > Spark settings > Environment:
Set default environment to: On and select the correct environment.

After changing the environemnt you need to do a publish in each workspace again but all notebooks keep working without needing the sparkenvironment ID. 

Even if someone else edit the notebook and you sync it again from devops it works.

Only everyone should have the same settings in there workspace.

[chetnachaudhari]

@Anonymous could you please update us on the roll out of this feature. We use australiaeast region, and I still get this error when I deploy an environment attached notebook from one workspace to another.

[chetnachaudhari]

Hi @Anonymous ,

I can see the environments are now supported using deployment pipelines, but after deployment notebooks are unable to pick the deployed environment, I see following error.

Thanks,

Chetna

[chetnachaudhari]

@Anonymous  Is it supported now, I still couldn't find any setting / rule to attach environment name in another workspace.

[Anonymous]

Hi @chetnachaudhari ,

The deployment pipeline support haven't been available. The feature roll out is starting soon.
In the next two weeks, it should be available in most production regions.

Thank you

[Anonymous]

Hello @Anonymous,

Thank you for the update. It's good to know about the progress. Please do keep me informed about any further developments regarding this matter.

[Anonymous]

Hi @Anonymous ,

For your information, I will post any further updates from my internal team here.

Hopefully I answered your query! Please continue using Fabric Community for your further queries.

[Anonymous]

Hello @Anonymous ,

Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.

[afraaij_Amphia]

I see the Environment in a Notebook is pointed to based on a GUID and that changes during deployment when deployed to the other workspaces but not in the Notebooks.

How are you going to solve this?

[Anonymous]

Hi @Anonymous ,

We have an update from internal team -

For now user needs to munally update the attached env to the one in the same workspace.

 We target to support Env in deployment pipeline by end of March. After that, the attached Env of a NB can be reproduce in the destination workspace.  

---

Hope this is helpful. Please let me know incase of further queries.