microsoft / coe-alm-accelerator-templates

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

coe-alm-accelerator-templates's Issues

Pack solution from repo

I've seen in your export-solution.yml template you only extract the exported unmanaged solution file to repo.
In your pipeline template build-solution.yml you pack the managed and unmanaged solution based on the solution folder in the repo.

Please correct me if I'm wrong:

• an unmanaged solution never contains any deletions/component deactivations like deactivated forms and views etc.
• when you pack your managed solution using the repo folder with the unmanaged solution content the information about the deactivations is missing and so in your target environment the deactivations will never happen

Do I miss something?

Pipelines: Update build pipeline for PRs to not use build completion triggers

Related issue microsoft/coe-starter-kit#160

Flows with no connection references fail to activate

If a flow doesn't contain any connection references it will fail to activate and the pipeline fails. Check for empty $impoersonationCallerId in update-connection-references.yml and only attempt to use impersonation if not empty otherwise activate the flow using the SP connection.

Please File Issues at https://github.com/microsoft/coe-starter-kit/issues

For issues related to microsoft/coe-alm-accelerator-templates please create them at https://github.com/microsoft/coe-starter-kit/issues

Flow Activation - Flow is missing Connection exception

When the pipeline tries to activate the Flow after reassigning the ownership, I get the exception below

The connection references are owned by the service account. I created the connections in the destination environment and use the ConnectionReferences pipeline variable to hook this up with the connection reference. I also made sure that the unique name of the connection reference and the actual connection id are correct in the JSON being passed.

When the Pipeline tries to reassign the Flow to a real user and then activate it, the Pipeline fails with the error in the 1st screenshot.

When I tried to run the reassign/activate script update-connection-references.yml locally, I get the same error

If I try to activate the Flow on the portal I get the same error as well.

I read again and I can confirm that:

1. Connection Reference records have been created in destination environment
2. Connection Reference record is owned by service account configured in the pipeline
3. Connections exists in the destination environment
4. Connection is owned by my SysAdmin account in the destination environment
5. Connection and Connection Reference are hooked up (manually) in the destination environment

I am not sure what I am missing.

Testing Teams Integration

Paths do not match when exporting and importing managed solution

coe-alm-accelerator-templates/Pipelines/delete-unmanaged-solution-and-components.yml

Line 138 in 851cd07

SolutionInputFile: '$(Pipeline.Workspace)\${{parameters.SolutionName}}.zip'

Does not include \exported, but the previous stage creates the managed solution in the \exported folder.