The ability to parameterize the connection would enable using separate identities (e.g. separate service principals) for dev/test/prod environments.
Having to use the same SPN in dev/test/prod introduces unnecessary risks, like accidental data modification across environments - a dev workload accidentally writing to production data, or a production workload accidentally connecting to and using data from the dev environment.
This would be solved if we could use variable library to reference the corresponding connection id for dev/test/prod service principal.
Unfortunately, the connection property in pipeline's notebook activity does not support Dynamic Content yet.
Please make this possible so we can avoid the risk of cross-contamination between environments.
on:
CI/CD support for Notebook Resources folder
tbindas-msft
on:
Add Object, Workspace and User details to Capacity...
on:
Variable Library: Shortcuts with variable value th...