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 your feature request related to a problem? Please describe.
With the changes made for sharing connections with service principals we no longer support using impersonation for Flow Activation. We need to remove this logic and some of the additional configuration options in the deployment settings that are no longer used.
Describe the solution you'd like
Remove impersonation related logic from pipelines and remove activation user from deployment settings. The following scenarios need to be verified.
Flows with connections / connection references
Flows with no connections / connection references.
Flows with owners specified in the deployment settings.
Flows without owners specified in the deployment settings.
Deploying to an environment where the user who owns the connections doesn't have access to the environment e.g. user's permissions have been removed after creating their connections.
Others...
Describe alternatives you've considered
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered:
@mikefactorial This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
Is your feature request related to a problem? Please describe.
With the changes made for sharing connections with service principals we no longer support using impersonation for Flow Activation. We need to remove this logic and some of the additional configuration options in the deployment settings that are no longer used.
Describe the solution you'd like
Remove impersonation related logic from pipelines and remove activation user from deployment settings. The following scenarios need to be verified.
Describe alternatives you've considered
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: