Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ALM Accelerator - QUESTION] Owner field within ALMA for Canvas Apps #9512

Open
ChristopheHare opened this issue Jan 17, 2025 · 1 comment
Open
Assignees
Labels
alm-accelerator ALM Accelerator Components and Apps question Further information is requested

Comments

@ChristopheHare
Copy link

What is your question?

Hi team,

Just a question on the Solution Component Ownership.

Am i missing something? there is no owner field within ALMA for Canvas Apps.

Image
And the pipeline states "Skipping this for workflow ALMATesting."

Image
Meaning the owner is set to the SP or App Reg

Image
The SP or App reg is also being set for other components within the solution.

Image
The only value for ownership that has been set is the Cloud Flow, as this has been set within the App.

Apologies if i have missed something, i've been through the material on MS Docs countless times, still finding new things, but this issue has eluded me for some time now.

As usual, any help is greatly appreciated.

Thanks,
Chris

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20240305.1(Managed)

@ChristopheHare ChristopheHare added alm-accelerator ALM Accelerator Components and Apps question Further information is requested labels Jan 17, 2025
@Grant-Archibald-MS Grant-Archibald-MS changed the title [ALM Accelerator - QUESTION] QUESTION [ALM Accelerator - QUESTION] Owner field within ALMA for Canvas Apps Jan 17, 2025
@Grant-Archibald-MS
Copy link
Collaborator

@ChristopheHare Due to limited capacity our core focus on the ALM Accelerator is looking at integration with Pipelines for Power platform and native source control integration.

To give context historically we have used the ALM Accelerator for deployment of the CoE Kit to GitHub we are transitioning this process to make greater use of Native Source Control integration and Pipelines as out of the box features rather than using the ALM Accelerator.

Given this we are addressing only a small number of issues related to the ALM Accelerator depending on priority and specifically prioritizing those that as extensions of pipelines. For example:

  • Extension of DevOps pipelines to execute unit and integration tests.
  • The process to push changes to upstream repositories
  • The ability to publish a release as a GitHub release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alm-accelerator ALM Accelerator Components and Apps question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants