Great Video Mike. SHould there is one ALM Accelerator in one environment open to everyone in the organization? I am trying to understand the working of it, do makers open the tool and they see only the solution they have access to?
Great question! Yes, generally speaking you would have a single ALM Accelerator in one environment. Your developers / makers would only have limited access to that environment. Subsequent to this video, a new Power Platform ALM pipeline solution has gained some traction as well. Check out the link below for details on this. This option is a bit simpler to employ, does not leverage DevOps and is essentially self contained in a dedicated "host" ALM environment. Makers can leverage the pipelines option within their unmanaged solution to deploy the solution to a target environment. Definitely worth a look if you don't need a DevOps or Git repo. learn.microsoft.com/en-us/power-platform/alm/pipelines Another high level way to think of these two options... The first option (using a DevOps or Git repo) is useful for distributed no code development where you need to manage merges, branches, etc. and / or you care about connecting changes to work items. The second option works well if you don't care about those things as much and you're doing development in a shared dev environment and just need to manage deployment from dev -> test -> prod.
Helped a lot. One question : Is it possible to bypass the validation when a user submit a deployment to Test environment ? I just need a validation when he want to deploy his apps to production environment
Yes, you can do this! The example used for this post was the "template" that comes as part of the COE solution. It is intended as a model to work from, not the perfect implementation for everyone. You would need to make some updates to how the pipelines work in Azure DevOps, and you might need to update the app as well to accommodate this.
Great walk through Mike! I love the conversational style of the video. I noticed that you called the second section "App Lifestyle Management" instead of "App Lifecycle Management". I don't know if that was intentional or not, but I LOVE it :)
The ALM Toolkit is not especially configurable. It is intended to be a template for you to develop your own tools that fit with your ALM process. This means you can 100% do what you are trying to do, so we would suggest using Microsoft documentation and the example in the ALM Toolkit to make the adjustments. It will likely require some tweaks to the two Canvas Apps as well as the YAML pipelines. This may be something we would consider building a course for since it is a bit involved if there is enough interest. docs.microsoft.com/en-us/power-platform/guidance/coe/almacceleratorpowerplatform-components
Great Video Mike. SHould there is one ALM Accelerator in one environment open to everyone in the organization? I am trying to understand the working of it, do makers open the tool and they see only the solution they have access to?
Great question! Yes, generally speaking you would have a single ALM Accelerator in one environment. Your developers / makers would only have limited access to that environment.
Subsequent to this video, a new Power Platform ALM pipeline solution has gained some traction as well. Check out the link below for details on this. This option is a bit simpler to employ, does not leverage DevOps and is essentially self contained in a dedicated "host" ALM environment. Makers can leverage the pipelines option within their unmanaged solution to deploy the solution to a target environment. Definitely worth a look if you don't need a DevOps or Git repo.
learn.microsoft.com/en-us/power-platform/alm/pipelines
Another high level way to think of these two options...
The first option (using a DevOps or Git repo) is useful for distributed no code development where you need to manage merges, branches, etc. and / or you care about connecting changes to work items.
The second option works well if you don't care about those things as much and you're doing development in a shared dev environment and just need to manage deployment from dev -> test -> prod.
Helped a lot. One question : Is it possible to bypass the validation when a user submit a deployment to Test environment ? I just need a validation when he want to deploy his apps to production environment
Yes, you can do this! The example used for this post was the "template" that comes as part of the COE solution. It is intended as a model to work from, not the perfect implementation for everyone. You would need to make some updates to how the pipelines work in Azure DevOps, and you might need to update the app as well to accommodate this.
Great walk through Mike! I love the conversational style of the video. I noticed that you called the second section "App Lifestyle Management" instead of "App Lifecycle Management". I don't know if that was intentional or not, but I LOVE it :)
Thanks Chris! Good catch! We missed that in editing but we kind of like it too 😊
What is the procedure to add additional environment? We have additional SIT environment . In such case how can we implement ALM accelerator?
The ALM Toolkit is not especially configurable. It is intended to be a template for you to develop your own tools that fit with your ALM process. This means you can 100% do what you are trying to do, so we would suggest using Microsoft documentation and the example in the ALM Toolkit to make the adjustments.
It will likely require some tweaks to the two Canvas Apps as well as the YAML pipelines. This may be something we would consider building a course for since it is a bit involved if there is enough interest.
docs.microsoft.com/en-us/power-platform/guidance/coe/almacceleratorpowerplatform-components
Thank you my friend, this helped me a lot
No problem, glad we could help!
Excellent !!
Thanks Abdul!