Create/update/share/delete Connections [with Service Principal] via PAC CLI #481
Replies: 10 comments 4 replies
-
Where can I give this +1000 upvotes? 😆 |
Beta Was this translation helpful? Give feedback.
-
@jboliveira Thanks for very detailed suggestion |
Beta Was this translation helpful? Give feedback.
-
+1 |
Beta Was this translation helpful? Give feedback.
-
I see connection related stuff in featureflags. Is this being worked on @petrochuk @kkanakas? |
Beta Was this translation helpful? Give feedback.
-
@rajyraman this discussion has highest number of votes so far. That means we are going to be looking at implementing some of these suggestions. |
Beta Was this translation helpful? Give feedback.
-
Sneak peek Create Entra ID application and create connection using it |
Beta Was this translation helpful? Give feedback.
-
We will start with Dataverse connections using Service Principals and expand based on your feedback |
Beta Was this translation helpful? Give feedback.
-
@kkanakas @petrochuk |
Beta Was this translation helpful? Give feedback.
-
I'll close this item. I understand it is not yet complete, but we made enough progress and can treat any improvements as separate discussions with links to this one. |
Beta Was this translation helpful? Give feedback.
-
@petrochuk does the pac connection update command support converting a connection to use a app registration service principal instead of a current user setup? I tried it out and it said it was successful but when I went to the UI to look at the connection, it didn't seem to be updated. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Context
Currently, as indicated in discussion #452, we experience difficulties maintaining Dataverse connections, particularly those created with Service Principals.
Given that Service Principal rotation is strongly encouraged to be performed on a regular basis for security reasons, it also leads to nested operations, such as the regeneration of the connection with the new
clientSecret
, obtain the newconnectionId
to be placed in thedeploymentSettings.json
, re-deploy the solution with the new connection Ids, and so on.It's also worth noting that creating a Dataverse connection with Service Principal is only feasible during the establishment of a fake flow, which won't even be saved at the end.
Idea
Would be ideal if we could create/update/share/delete connections with Service Principal (if applicable) using PAC CLI.
Commands
pac connection
Usage:
pac connection [create] [update] [share] [delete] [show] [list]
create
update
share
delete
show
list
pac connection create
Usage:
pac connection create [--name] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--connectionType]
--name
--username
--password
--applicationId
--clientSecret
--tenant
--connectionType
Example: Named Create with Service Principal
pac connection update
Usage:
pac connection update [--name] [--username] [--password] [--applicationId] [--clientSecret] [--tenant]
--name
--username
--password
--applicationId
--clientSecret
--tenant
Example: Update Connection with Service Principal
pac connection share
Usage:
pac connection share [--name] [--servicePrincipal]
--name
--servicePrincipal
Example: Share Connection with Service Principal
pac connection delete
Usage:
pac connection delete [--name]
--name
Example: Delete Connection
pac connection show
Usage:
pac connection show [--name]
--name
Example: Show Connection
pac connection list
Usage:
pac connection list
Further deep dives are encouraged.
Beta Was this translation helpful? Give feedback.
All reactions