[ALM Accelerator - Feature]: Add option to select business unit for group teams #3393
Assignees
Labels
Milestone
Comments
ryanhodgson1
added
alm-accelerator
mikefactorial
added a commit
that referenced
this issue
Oct 4, 2022
* Fixes #3393 * Custom connector update * Testing pipeline bug fix * Add AzureDevOps project page and dependencies (#3770) * policy to change http method, runsyncpipeline (#3768) * add processed canvas app (custom page) * rename custom page * Set solution type <Managed/> to both * add managed appmodule files * fix pipeline template version var * minor fixes and app rename * remove GetPipelineRunResult * remove remaining bits of GetPipelineRunResult * fixes #3673 * fixes #3800 remove home, pinned and recent * fixes #3799 add refresh release tags * minor fixes and enhancements * fix refresh icon positions * fix non admin scenario * more fixing of non admin scenario * new wizard UI * remove app reg vars in CreateVariableGroup params * Remove VariableGroup from wizard * use url for svc conn names * several minor fixes and ui improvements * Revert version number to 0.0.0.0 * remove connection parameters * fix for existing pipeline projects * fixing wizard button label * fix external template project permissions * Service account permissions fix * Exporting with new structure * Removing test deployment Co-authored-by: Johanna Lorenz <JohannaL@PPlatform.OnMicrosoft.com> Co-authored-by: jenschristianschroder <jeschro@microsoft.com> Co-authored-by: CoEStarterKitBot <coebot@outlook.com>
|
@ryanhodgson1 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us. |
ChristopheHare
pushed a commit
to ChristopheHare/coe-starter-kit
that referenced
this issue
Sep 7, 2023
* Fixes microsoft#3393 * Custom connector update * Testing pipeline bug fix * Add AzureDevOps project page and dependencies (microsoft#3770) * policy to change http method, runsyncpipeline (microsoft#3768) * add processed canvas app (custom page) * rename custom page * Set solution type <Managed/> to both * add managed appmodule files * fix pipeline template version var * minor fixes and app rename * remove GetPipelineRunResult * remove remaining bits of GetPipelineRunResult * fixes microsoft#3673 * fixes microsoft#3800 remove home, pinned and recent * fixes microsoft#3799 add refresh release tags * minor fixes and enhancements * fix refresh icon positions * fix non admin scenario * more fixing of non admin scenario * new wizard UI * remove app reg vars in CreateVariableGroup params * Remove VariableGroup from wizard * use url for svc conn names * several minor fixes and ui improvements * Revert version number to 0.0.0.0 * remove connection parameters * fix for existing pipeline projects * fixing wizard button label * fix external template project permissions * Service account permissions fix * Exporting with new structure * Removing test deployment Co-authored-by: Johanna Lorenz <JohannaL@PPlatform.OnMicrosoft.com> Co-authored-by: jenschristianschroder <jeschro@microsoft.com> Co-authored-by: CoEStarterKitBot <coebot@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
There is currently no way to choose what business unit to put the group teams into when adding them to the ALM app environment deployment settings.
Describe the solution you'd like
Add a field in the ALM apps page for group teams to input a business unit and pass it as a variable to the file set-dataverse-aad-group-teams.yml. I have added the relevant code to the file in my pull request to be able to pull it through but the variable in the ALM app still needs to be put in so its pulled through.
Describe alternatives you've considered
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: