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 - BUG]: Two solutions with same name has same deployment profile #5350

Closed
jenschristianschroder opened this issue Apr 21, 2023 · 3 comments · Fixed by #5712
Assignees
Labels
alm-accelerator ALM Accelerator Components and Apps bug Something isn't working

Comments

@jenschristianschroder
Copy link
Contributor

Describe the issue

If two solutions in each their own environment have the same name, they will automatically share the same profile and deployment history.

Here is ALMOnboardingTestSolution in DEV environment with DEV profile. Solution has been committed and deployed already
image

Here is ALMOnboardingTestSolution in DEV2 environment. Solution has never been committed or deployed. By default it inherits the DEV profile due to have same solution name
image

Assigning new DEV2 profile to solution in DEV2 environment results in same profile settings for solution in DEV environment

Expected Behavior

Expect that it is possible to have solutions with same name in different environments and that changes to profile, deployment request and other is specific to the solution in the respective environment

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20230405.2

Steps To Reproduce

No response

Anything else?

No response

@jenschristianschroder jenschristianschroder added bug Something isn't working alm-accelerator ALM Accelerator Components and Apps labels Apr 21, 2023
@Palkn
Copy link

Palkn commented Jun 1, 2023

We are experiencing the same issue. Any news on fixing this?

@mikefactorial
Copy link
Contributor

Looking into a fix for this in the upcoming June release.

CoEStarterKitBot pushed a commit that referenced this issue Jun 1, 2023
RajeevPentyala pushed a commit that referenced this issue Jun 6, 2023
* Fixes #5350

* Update to use environment id instead of uniquename

---------

Co-authored-by: Michael Peltier <Michaelp@powercattools.onmicrosoft.com>
@CoEStarterKitBot
Copy link
Collaborator

@jenschristianschroder 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#5350

* Update to use environment id instead of uniquename

---------

Co-authored-by: Michael Peltier <Michaelp@powercattools.onmicrosoft.com>
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 bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants