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

Allow for centralized configuration #565

Closed
afeld opened this issue Oct 17, 2022 · 2 comments · Fixed by #573
Closed

Allow for centralized configuration #565

afeld opened this issue Oct 17, 2022 · 2 comments · Fixed by #573
Labels
enhancement New feature or request
Milestone

Comments

@afeld
Copy link

afeld commented Oct 17, 2022

Is your feature request related to a problem? Please describe.

I have separate notebooks for each assignment, but they are generally structured the same. This means copying configuration options across all of them.

Describe the solution you'd like

I'd like to be able to specify configuration options in a single place, ideally in a config file. CLI arguments would work as well.

Describe alternatives you've considered

The documentation references otter_config.json, which may solve this problem, but I'm not seeing any documentation about the possible values of that file.

Additional context

#395 may be related.

@afeld afeld added the enhancement New feature or request label Oct 17, 2022
@chrispyles
Copy link
Member

Documentation for the keys available in otter_config.json can be found here but I don't think this will do what you want -- this is a file generated by Otter Assign based on the configurations in your assignment config. I think allowing this to be specified in a separate file is a good idea.

@chrispyles
Copy link
Member

Support for these files was implemented in #573. To use this functionality, specify a config_file in your assignment config:

# ASSIGNMENT CONFIG
config_file: assignment_config.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants