vcs:gitlab_roster_usage
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vcs:gitlab_roster_usage [2020/09/16 15:40] – [Controlling The Rosters] chudler | vcs:gitlab_roster_usage [2020/09/16 16:17] (current) – chudler | ||
---|---|---|---|
Line 28: | Line 28: | ||
The overall automation tool is controlled by Techstaff. It must be enabled **before** you can modify the provisioner' | The overall automation tool is controlled by Techstaff. It must be enabled **before** you can modify the provisioner' | ||
- | ====Internal | + | =====Repo-based |
- | Before | + | Before the automations creates the first repository, it can be configured to read data that is published in **your own** secure Gitlab repository. |
- | Every hour, the automations bot will checkout the head of your '' | + | Every hour, the automations bot will checkout the head of your '' |
- | Because of Roster Config Merging, you typically only need to //augment// the Registrar' | + | Because of the aforementioned |
- | It is also possible to specify partial information, | + | It is also possible to specify partial information, |
+ | |||
+ | =====File Format===== | ||
+ | |||
+ | Files must end in a '' | ||
+ | |||
+ | All structures must begin with a key that uniquely and globally identifies the course and offering that is currently being taught. The format of the key is opaque to the provisioner and is not parsed, and you are also not restricted to choosing from known keys. Therefore, you are able to create repositories that have no upstream datasource, for testing, future use, and other devices. The example below uses a familiar key structure intended for real courses. | ||
< | < | ||
Line 49: | Line 55: | ||
</ | </ | ||
- | An example to create course without any associated Registrar data is the same, but includes | + | When your configuration is split across multiple files, merging takes place on the basis of the key. So, be sure to use the same key in different '' |
- | more memberships | + | |
+ | An example to create | ||
< | < | ||
Line 69: | Line 76: | ||
</ | </ | ||
- | ==Configuration Merging== | + | As the example shows, the automations will consume this structure and map the groups of people (" |
+ | |||
+ | ===Configuration Merging=== | ||
Techstaff will augment any configuration you provide with roster data from the University Registrar. The union of memberships is considered, and scalar values are overridden by your values. | Techstaff will augment any configuration you provide with roster data from the University Registrar. The union of memberships is considered, and scalar values are overridden by your values. | ||
[[More Roster Configuration Examples]] | [[More Roster Configuration Examples]] | ||
/var/lib/dokuwiki/data/attic/vcs/gitlab_roster_usage.1600288829.txt.gz · Last modified: 2020/09/16 15:40 by chudler