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]: Issue with sharing connection with SPN when moving to Test Environment #7369

Closed
groypk opened this issue Jan 3, 2024 · 10 comments
Assignees
Labels
alm-accelerator ALM Accelerator Components and Apps bug Something isn't working

Comments

@groypk
Copy link

groypk commented Jan 3, 2024

Describe the issue

Noticed this for a few deployments, users have updated the Deployment Settings correctly for connection references and clicked on SHare ALl to share the connection with the SPN, but the deployment still fails in Test Environments saying the spn does not have the needed access.

As a workaround when I manually go into the Test environment and share the connection with the SPN it works.

Expected Behavior

No response

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20231012.1

Steps To Reproduce

  1. Go to ALM Acc App
  2. Choose your Deployment User and Dev Environment
  3. Set the Deployment Profile
  4. GO to your solution and update the Deployment Settings
  5. Create and share your connection reference with the SPN
  6. Commit the solution
  7. Deploy to Test ( fails because cannot detect shared connection)
  8. Deploy to Prod works

Anything else?

image

AB#1933

@groypk groypk added alm-accelerator ALM Accelerator Components and Apps bug Something isn't working labels Jan 3, 2024
@RajeevPentyala
Copy link
Collaborator

@groypk Issue might be similar to #6971 when there are multiple connections. This has been addressed and will be available in the next release.

@groypk
Copy link
Author

groypk commented Jan 4, 2024

@groypk Issue might be similar to #6971 when there are multiple connections. This has been addressed and will be available in the next release.

Hi Rajeev, I had a look at the bug, in their case the connections are all pointing to one, in ours the connection is not being shared with the Service Principal at all even when Share All has been entered, could be related to the config file settings

@RajeevPentyala
Copy link
Collaborator

@groypk Can you confirm if you've shared the connections with the 'Deployment User' before deploying the solution?. In order for your solution to be deployed successfully your connection(s) must be shared with the deployment user (i.e., Your pipelines service connection principal user). Please be aware that simply checking the 'Share All' checkbox in 'Deployment settings' won't work unless you manually share the connections with the 'Deployment User'.

image

@groypk
Copy link
Author

groypk commented Jan 4, 2024

@groypk Can you confirm if you've shared the connections with the 'Deployment User' before deploying the solution?. In order for your solution to be deployed successfully your connection(s) must be shared with the deployment user (i.e., Your pipelines service connection principal user). Please be aware that simply checking the 'Share All' checkbox in 'Deployment settings' won't work unless you manually share the connections with the 'Deployment User'.

image

Hi Rajeev, we don't manually share the connections in Production, and the flows work, from what I understand the tool takes care of this and there is no need to manually share the connections with the SPN? This is what we have been following and the pipelines have worked until recently where a few users reported this issue, then having the share button defeats the purpose right?

@RajeevPentyala
Copy link
Collaborator

@groypk When I mention that the connection needs to be shared manually, users must select the 'Share' or 'Share All' checkbox, which you are already doing according to the issue description.

After selecting 'Share' and saving the settings, can you confirm if the 'ShareConnectionWithServicePrincipal' flow is triggered?. 'ShareConnectionWithServicePrincipal' is the flow comes with 'ALM Accelerator' solution.

image

@groypk
Copy link
Author

groypk commented Jan 19, 2024

HI @RajeevPentyala , I do see flow runs in history but will confirm if it runs every time I save the settings.

@groypk
Copy link
Author

groypk commented Feb 6, 2024

Hi @RajeevPentyala , the flow is running but not always, looks like the trigger may not be working , as a work around we have been manually sharing the connections, is there anything we can do to address this? We had a new user deploy this week and there are no flow runs for that

image

@RajeevPentyala
Copy link
Collaborator

@groypk The 'ShareConnectionWithServicePrincipal' flow runs every time you save the configuration settings and if the following criteria are met.

  • 'Share' checkbox is checked.
  • Connections has to be resolved. You should see 'Connected' as highlighted below.

Can you confirm if the above-mentioned criteria were met in your scenario?

image

@RajeevPentyala
Copy link
Collaborator

@groypk Closing this issue as there was no update. Please reach out if you need further assistance.

@tobiasneunercs
Copy link

@RajeevPentyala We have a similar issue in our test of the ALM accelerator.
The connection reference is stated as "Connected" and the checkbox is checked. But the 'ShareConnectionWithServicePrincipal' flow is not getting triggered.
Any ideas, what might be the issue?

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

No branches or pull requests

3 participants