Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

[IDEA] Use of a JSON template file of the Power Platform environment in the provisioning pipeline #16

Open
rpothin opened this issue Oct 10, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request pipeline This issue or pull request concerns a pipeline definition

Comments

@rpothin
Copy link
Member

rpothin commented Oct 10, 2020

One way to simplify the provisioning of a Power Platform environment could be to reduce the number of input variables needed for the create-powerplatform-environment-and-service-endpoint pipeline.

I think that a template file in JSON could be a good way to manage the properties of the Power Platform environment.
This template file would be then consumed by the create-powerplatform-environment-and-service-endpoint pipeline (path to the file provided as a variable).

@rpothin rpothin added enhancement New feature or request pipeline This issue or pull request concerns a pipeline definition labels Oct 10, 2020
@rpothin rpothin self-assigned this Oct 10, 2020
@rpothin
Copy link
Member Author

rpothin commented Dec 13, 2020

For the moment, I will try to use a variable group (library) to share variables across different pipelines.
Note to myself: need to update the README.md file regarding this new way to work with common variable.

@BenediktBergmann
Copy link
Member

I think a variable group could be good here. Might be an idea to use the approach we fell most comfortable with to get a first working version and possibly change it to the preferred method later.

@rpothin
Copy link
Member Author

rpothin commented Dec 13, 2020

I will make some updates in the current PR to use a variable groups.

It will have some impacts in the pipelines and in the README.md file.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request pipeline This issue or pull request concerns a pipeline definition
Projects
None yet
Development

No branches or pull requests

2 participants