Skip to content

ALM Accelerator For Advanced Makers July 2021

Pre-release
Pre-release
Compare
Choose a tag to compare
@mikefactorial mikefactorial released this 27 Jul 14:24
· 672 commits to main since this release
ALMAcceleratorForAdvancedMakers-July2021
0266d25

[!IIMPORTANT] This release includes the use of an update in the platform that will not be released to the following geos (SPL, GCC, USG, CHN) until the last week in July. If you are using AA4AM in one of these geos please wait to upgrade until August 1st 2021.

Issues and new features in this release:

https://github.com/microsoft/coe-starter-kit/milestone/10

First Time Setup Instructions

To get started with the ALM Accelerator For Advanced Makers you can

  1. Use the preview CoE CLI to automate the install at https://github.com/microsoft/coe-starter-kit/blob/main/coe-cli/docs/aa4am/readme.md or in the Power Platform CoE CLI E-Book
  2. Use the manual setup documentation can be found at https://github.com/microsoft/coe-starter-kit/blob/main/ALMAcceleratorForAdvancedMakers/SETUPGUIDE.md

Upgrade Instructions

If you are upgrading to the latest release you will need to perform the following steps.

  • Import the latest AA4AM Solution https://github.com/microsoft/coe-starter-kit/releases/download/ALMAcceleratorForAdvancedMakers-July2021/ALMAcceleratorForAdvancedMakers_1.0.20210727.1_managed.zip

  • Update your pipeline templates repo with the latest from https://github.com/microsoft/coe-alm-accelerator-templates

  • Export solutions with Canvas Apps using latest version of AA4AM.

    [!NOTE] AA4AM use a preview version of the Power Apps Source File Pack and Unpack Utility (https://github.com/microsoft/PowerApps-Language-Tooling/blob/master/README.md). As such while AA4AM is still in public preview we are updating our pipelines to stay in sync with the latest releases of the Pack / Unpack utility. The Pack / Unpack utility is not backwards compatible while in preview meaning the version used to unpack must be the same as the version used to pack. If you have previously unpacked Canvas Apps using a previous version of AA4AM you will not be able to repack those apps. Therefore, you must export your solutions to source control again using the latest version so the formats match. We are planning on providing backward compatibility going forward after this release #895.

  • In this release we have updated the pipelines to allow for using a deployment configuration file stored in source control as an option rather than using Pipeline variables for the json configuration of Connection References, Component Ownership, App Sharing etc. There is a new doc included on how to setup your deployment configuration file and use variable substitution techniques to secure sensitive data from being source controlled. DEPLOYMENTCONFIGGUIDE.md.

    [!NOTE] If you have previously configured your pipelines using pipeline variables you are not required to switch to using the deployment configuration file and the pipelines will continue to fall back to using pipeline variables in the absence of a deployment configuration file for the environment to which a solution is deployed. However, future updates to the Power Platform build tool will be reliant on a deployment configuration file so you may want to consider moving to this standard now.

  • The list of Azure DevOps extensions required for the AA4AM pipelines has been updated. Double check this list to ensure you have the correct extensions installed. Any extension that has been removed from the list can be safely removed Install Azure DevOps Extensions.

Change Log

  • #27-[AA4AM] Pipelines: import-unmanaged-to-dev-environment - handle setting environment variables and connection references for empty environments
  • #33-Setup automation based on the GETTINGSTARTED.md procedure
  • #78-Custom Connector oauth settings break after Solution Import
  • #115-Pipelines: Make Data Import Specific to Environment
  • #121-Pipelines: Exclude Environment Variable Values from Source Control
  • #122-AA4AM App: Update Solution Import Experience
  • #123-AA4AM App: Update AA4AM User Role Permissions
  • #331-[Documentation] Add App User Troubleshooting to SETUP doc
  • #390-[AA4AM] Show environment banner in app
  • #489-[AA4AM] Align Issue Templates for ALM Accelerators with CoE Starter Kit
  • #513-[AA4AM] July Release Documentation Updates
  • #523-[AA4AM] Replace temp-canvas-packager
  • #560-[AA4AM] handle spaces in project name
  • #561-[AA4AM] Add placeholder replacement to source controlled configuration
  • #589-[AA4AM] Add Creation of GitHub Release to pipelines
  • #596-[AA4AM] Replace RegEx Extension
  • #600-[AA4AM]: Solution not appearing after import
  • #607-[AA4AM] Export Solution to Git error
  • #616-[AA4AM]: Wiping out connections json is causing errors on solution deployment
  • #635-[ALM Accelerator - BUG]: Default Branch May Not Be main When Cloning Pipelines
  • #636-[ALM Accelerator - BUG]: Setup Documentation Sequencing - Create Pipeline Global Variables before Service Connections Created
  • #643-Prod template references Validation in comment
  • #697-[AA4AM]: Check Default Value of specified environment variables
  • #698-[AA4AM]: Check no current value is present for environment variables on release
  • #706-[ALM Accelerator - BUG]: Error at the build-deploy "pack msapp files" step
  • #785-[AA4AM] Creating a Release should close and comment on completed items
  • #802-[ALM Accelerator - BUG]: Update Solution Component Ownership Failed
  • #844-[AA4AM] - Make docs more clear that we're in public preview
Assets 6
Loading