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

Support new pycue configuration paths. #972

Merged

Conversation

bcipriano
Copy link
Collaborator

Link the Issue(s) this Pull Request is related to.
#785

Summarize your change.
The user-visible change here is there are a few new ways to define the config used by the opencue library (and anything that depends on it e.g. CueGUI):

  • OPENCUE_CONFIG_FILE can be used to point to the YAML config file.
  • ~/.config/opencue/opencue.yaml is used as a default path for the YAML config (this uses %APPDATA% on Windows).
  • Existing config methods i.e. OPENCUE_CONF are still supported.

To achieve this there are a few minor changes:

  • Add a few basic unit tests for opencue.cuebot to make sure we're not breaking anything.
  • Split config file ingestion into a new opencue.config module, and have opencue.cuebot utilize this.
  • Modify the behavior of opencue.config to support the new environment variable and default path.
  • Add some unit tests for opencue.config to test the new code.

@bcipriano bcipriano marked this pull request as ready for review June 5, 2021 18:41
@bcipriano
Copy link
Collaborator Author

I've tested this on Mac and Windows now, ready for review.

@bcipriano
Copy link
Collaborator Author

Last call for review here before I merge. Changes have been discussed by the TSC so I don't think there's anything controversial here.

@bcipriano bcipriano merged commit 6e302cb into AcademySoftwareFoundation:master Jul 29, 2021
@bcipriano bcipriano deleted the pycue-config-cleanup branch July 29, 2021 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant