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

Refresh and enrich ServiceGroups from sample data #416

Closed
3 tasks done
gregcorbett opened this issue Jan 13, 2023 · 0 comments · Fixed by #470
Closed
3 tasks done

Refresh and enrich ServiceGroups from sample data #416

gregcorbett opened this issue Jan 13, 2023 · 0 comments · Fixed by #470
Assignees
Labels
enhancement good first issue Issues that require "minimal" knowledge of the codebase hackathon Issues that could be solved within a day

Comments

@gregcorbett
Copy link
Member

gregcorbett commented Jan 13, 2023

Follows on from #394

  • Extend lib/Doctrine/deploy/AddServiceGroups.php so that it can create ServiceGroups that actually contain Services
  • Add lib/Doctrine/deploy/AddServiceGroupRoles.php so that ServiceGroup level roles can be created.
  • Refresh lib/Doctrine/deploy/sampleData/ServiceGroups.xml and /lib/Doctrine/deploy/sampleData/ServiceGroupRoles.xml to be consistent with the rest of the sample data.

The best way to tackle this may be to deploy the existing sample data to an instance, create some ServiceGroups in the UI, then use the API output to update the ServiceGroups.xml. Because the GOCDB UI doesn't let you request a role on behalf of a user, ServiceGroupRoles.xml can start from the API output but then it will have to be manually updated to include user roles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement good first issue Issues that require "minimal" knowledge of the codebase hackathon Issues that could be solved within a day
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants