Available Githubactions workflows usingbthe powerplatform-actions

[PrathapmM]

Hi @rpothin

Thank you so much for wonderful documentation in one place.

I would like to create the environments and export the solution and modify the code and import the solutions into the different environment and finally delete the newly created environment after merging the code.

Could you pls clarify me does powerplatform actions supports the environment creation through GitHub actions
To enable the dynamic 365 apps and deploy the Sales enterprise app?

[rpothin]

Hi @PrathapmM,

Thank you very much for this very positive feedback 😊

At a high level, the development process with a "just-in-time" development environment could indeed be the one your mentioned:

1. Creation of the development environment: workspace-initialization / create-environment
2. Import the solution you want to work on from the repository to the "just-in-time" development environment: workspace-initialization / pack-solution and import-solution
3. Update the solution in the "just-in-time" development environment: not applicable
4. Export the updated solution from the "just-in-time" development environment to the repository: export-and-unpack-solution / export-solution and unpack-solution
5. Delete the "just-in-time" development environment: clean-dev-workspace-when-issue-closed-or-deleted / delete-environment
6. Import the updated solution to other environments: import-solution-to-validation / pack-solution and import-solution

Note: For each step of this development process, I added the corresponding workflow in this repository and the key "out-of-the-box" Power Platform GitHub action(s).

Also, the create-environment "out-of-the-box" Power Platform GitHub action has the templates input that allows you to define the Dynamics 365 apps you want to install during the environment creation (I did not yet integrate this part in this repository but it is in the plan).

Note: I think for Dynamics 365 Sales, you should put D365_Sales in the templates input.

I hope all the details will help you.

Have a great day.
Raphael

[rpothin]

The create-environment action create the environment with the Dataverse database. In fact, the action does not propose an input to do it without the Dataverse database 😉

[PrathapmM]

The create-environment action create the environment with the Dataverse database. In fact, the action does not propose an input to do it without the Dataverse database 😉

Thank you @rpothin Appreciate your quick response as always. somehow i missed your comment. Sorry for coming again

1. Could you please suggest can i directly run this action ? i felt this does not have any triggers and runners defined.
2. how to call create environment action ? is it through yaml file needs to be added in workflow folder?

[rpothin]

Hi @PrathapmM,

To find the answer to this question, I think the best place would be the GitHub workflows documentation.

But in summary, the actions need to be added to a GitHub workflow (yaml file under the ".github/workflows" folder in your repository) and it is in the GitHub workflow you will define the trigger and runner.
GitHub actions are pieces you need to combine in GitHub workflows to build your automations.

I hope it will help.
Raphael

[wesco-prathapmotupalli]

Hi @PrathapmM,

To find the answer to this question, I think the best place would be the GitHub workflows documentation.

But in summary, the actions need to be added to a GitHub workflow (yaml file under the ".github/workflows" folder in your repository) and it is in the GitHub workflow you will define the trigger and runner. GitHub actions are pieces you need to combine in GitHub workflows to build your automations.

I hope it will help. Raphael

Thank you so much @rpothin Appreciate your quick response, Please take care!!

[rpothin]

You are welcome 🤗

Good luck for your implementation and have a great day.