Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Grouper Import-Export and managing objects

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Grouper Import-Export and managing objects


Chronological Thread 
  • From: Sean Mason <>
  • To: "" <>
  • Subject: [grouper-users] Grouper Import-Export and managing objects
  • Date: Mon, 14 Dec 2015 14:39:38 +0000
  • Accept-language: en-CA, en-US

Hi There,

I am looking at introducing Grouper to provide some access management
services for the campus, and am currently stuck trying to figure out how to
move stem structures and group definition objects between instances to manage
the development lifecycle of the product. This will be a new implementation,
using the latest released version of Grouper (2.2.2). I had sent this
question to the group early last week, but it seems to have been lost in the
shuffle or perhaps I'm just too impatient.

I am attempting to build a process that would allow migration of new stem
structures and preconfigured groups (like loader jobs) from development, to
test, to production. It would also be nice to be able to maintain an
external repository of these types of objects so that new environments may be
built in a more automated way. It seemed to me the Import-Export
functionality would be a good candidate for this, but I am either doing
something wrong, or it does not operate as I current understand.

An example: gsh -xmlexport -excludeAudits -objectNames
etc:LoaderJobs:SomeLoaderJob ~/SomeLoaderJob.xml The object in question is a
group definition with attribute values to configure a (successful)
SQL_GROUP_LIST loader job with no direct members.

My understanding of the documentation on
https://spaces.internet2.edu/display/Grouper/Import-Export made me believe
that the result would be an XML representation of the supplied group.
Instead the result is the export of a very large number (reportedly 600,000+,
though it "may be less") of objects that includes thousands of memberships,
audit events, and perhaps more since I haven't let a process complete through
the extraction of audit events.

Have I misunderstood what the xmlexport utility is for and how it works, or
perhaps I am doing something wrong? The inclusion of audit events alone
makes me believe I've missed something, since I thought I was explicitly
avoiding the extraction of that type of object with the -excludeAudits option.

If this is not the utility to perform such tasks, does the community have
suggestions on how this type of object management might be performed?

Thank you,
Sean




Archive powered by MHonArc 2.6.16.

Top of Page