DeployHubProject / DeployHub-Pro

DeployHub Pro Pipeline Status Project
https://www.openmakesoftware.com/application-release-automation-for-continuous-delivery/
Other
11 stars 4 forks source link

Objects not saving after new update #281

Closed piyush94 closed 4 years ago

piyush94 commented 4 years ago

Objects are not saving after the new update for the deployhub latest tag object-save-error-2 object-save-error

We tried with multiple objects such endpoint, credentials, etc. For Component this is coming: image

Kindly look into this on priority.

CC: @svisagan83

sbtaylor15 commented 4 years ago

@piyush94 please pull the latest image. The following objects had problems:

We could not recreate any issues with components or component items.

CC: @svisagan83

svisagan83 commented 4 years ago

@sbtaylor15
A component created from the Jenkins Build is not visible for the users who are part of that domain. only global administrators can able to view them

CC: @piyush94

sbtaylor15 commented 4 years ago

@piyush94 can you send a screen shot of the component detail showing the domain information and the access permissions?

cc: @svisagan83

piyush94 commented 4 years ago

@sbtaylor15 component: image

image

domain: image

image

cc: @svisagan83

sbtaylor15 commented 4 years ago

@piyush94 does creating a component at the same level as the missing one via the UI enable it to be visible to the non-global users? Trying to figure out which side the problem is stemming from, Jenkins or access control.

cc: @svisagan83

piyush94 commented 4 years ago

@sbtaylor15 rights don't seem to be working correctly. I am not able to create components from the UI even though i have access.

cc: @svisagan83

sbtaylor15 commented 4 years ago

@piyush94 what is the group membership for the userid that you are using?

cc: @svisagan83

piyush94 commented 4 years ago

@sbtaylor15 it’s in the StealthID-service-group with creation rights for components, applications and application versions.

CC: @svisagan83

sbtaylor15 commented 4 years ago

@piyush94 does adding the user to the administrators group fix the issue? This is just a test for debugging.

sbtaylor15 commented 4 years ago

Changed the domain level check to verify that the component domain matched the users domains.