Power Platform Pipelines - ALM became easier!
Vložit
- čas přidán 9. 07. 2024
- Hi! In this video I would like to share with you how to set up, configure and share Power Platform Pipelines as well to share my knowledge from using that new feature in production scenarios I learnt so far.
A very useful Q&A: learn.microsoft.com/en-us/pow...
Pipelines release plan: experience.dynamics.com/relea...
Chapters:
0:00 Intro
01:35 Set up Pipelines Host environment
02:40 Install Power Platform Pipelines application
03:35 Setup Deployment Pipeline Configuration application
04:30 Setup environments for Pipelines
07:27 Setup pipelines and configure stages
09:40 Share pipeline (incl. security roles)
12:33 Deploy a solution using Power Platform Pipelines - demo!
22:00 Brief description of a Dashboard in Deployment Pipeline Configuration app
23:55 Wrap up and lessons learnt!
Awesome Thanks.
Good video. Helped me out thanks.
Glad to hear it!
very interesting but a pemium licence for all user that are in the prod environnement. It well be more convenient if it was a premium licence based on the security role like Deployment pipeline users for example.
The point is, you don’t buy licenses just for the ALM. It’s an addition only. You buy them to build solution, use solutions, benefit from all premium features. That’s my point of view.
Hi Tomasz, thanks for the information, learning a lot from your videos. I have a question regarding to the deployment process. In your video you mention to clear the environment variables before deploying. Apparently, you have to do it each time you deploy a new version of the app. I've a small app with only 4 environment variables, but once I forgot to clear them and the SharePoint locations were changed to the SharePoint DEV locations. I'm wondering if there is an easy way to make sure the variables will not change each time you deploy a new version?
Thanks in advance.
No, you just need to do it once. And when you remove their values from the solution, they won't be there anymore unless you add them again.
Hi Tomaz, first thanks for sharing your knowledge.
I use the pipelines, but I noticed that even giving the values for the variables, in the case of SharePoint, both in the application and in the flows, the variables do not take the values, when I enter the APP the connections still maintain the value of the DEV environment, but when using the variable that went up to the solution, it takes the correct values.
Do you know if there is anything I need to configure so that this does not happen?
I am not sure I understood you correctly. In DEV env. you create variables, but before deploying the solution to PROD, you need to remove VALUES of these variables from the solution. During the deployment you'll be asked to provide values for these variables.
Thanks for sharing. Just a question, how do we move the lists for example which is used in FLOW between dev to test to prod SharePoint site? Is it possible using pipelines? If not what do you suggest as to how to move them. Thanks in advance.
You can't put that in solution. What you could try is to create a flow, that provisions a list. So that once a solution is deployed to test/prod you run a flow that creates the list and then you can update env. connection variables to point to that new list.
i thought the environments needed to have managed environments enabled but it seems to work for you even though they aren't? Any insight on this would be helpful!
The video was recorded with the preview version of a feature. And it only required managed env. for the one that has the pipelines solution installed.
From what I know managed env. is now required only for the production environment.
@@TomaszPoszytek do you limit sharing when you have managed env. enabled?
Hi Tomasz,
As a Power platform administrator I have configured Pipelines and granted Pipeline user & admin rights to makers. What permissions are required for the makers in UAT & Prod environment to run the pipeline and deploy apps in target environment? We use CoE ALM Accelerator and everything is done via Service principal (App registrations). How does permissions work for logged in user in target environment if the pipeline runs in the context of logged-in user?
They need regular env. maker permissions. Be sure you shared the pipeline with them.
The downside of pipelines is that it runs in a context of the user that triggered it. So it will be deployed using that same user in the target environment.
@@TomaszPoszytek One more question. Do you know if Host environment should be enabled as managed environment and it should be a dedicated environment. Microsoft docs says it should be not be a managed environment. We are repurposing CoE starter kit environment for pipelines and we have enabled this environment as managed.
@@kannank7313 during the preview it had to be managed. What I heard then was that the destination env. must be managed, but host not. Also, it is a good practice that the host is a dedicated env.
Hi Tomasz,
I am facing one minor issue which is after creating the environment variable. I create a Instant cloud Flow and then I used the mail action in which I used my email id and when I tried using the environment variable as Subject and tried saving the flow, it gave an error: Request to XRM API failed with error: 'Message: Flow client error returned with status code "Bad request" and details' Attribute value was not found (but in the video you did say that the value should be left blank)
Could you please help with this.
It should be filled with a value, but then the value should be "Removed from the solution".
@@TomaszPoszytek Okay will check by doing this.
Hi @Tomasz,
I created the environment variables by adding a custom value at start and then removed it from solution. Did not get any error while saving the Flow.
Now when I was trying to deploy it, now there are two options provided deploy now or later.
I selected Default option (now) and when it was validating the glow, it displayed missing dependency which was for sharedsendemail which is the environment variables I think but in the video you are connecting it and then assigning the value.
Let me know how to debug this.