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

osclib/conf: provide mechanism for staging specific setting overrides #1122

Closed
jberry-suse opened this issue Aug 31, 2017 · 0 comments
Closed
Assignees

Comments

@jberry-suse
Copy link
Contributor

Per mailing list discussion about how to handle ring packages whose install-time requirements are not in rings @DimStar77 requested to leave things as is and provide a way to keep a staging specific whitelist that is cleared on accept. This removes the need to whitelist problems, caused by stagings that have not been rebased, globally and instead can be restricted to individual stagings.

This feels like it could be done by extending remote config to provide staging specific overrides, but may end up being repo-checker specific. The ring command (#848) will work in similar manor, storing staging specific information that is cleared on accept, but the intention was to use psuedometa data. The two concepts are not that different, but if remote config either the entire global whitelist from the target project will need to be included along with the staging specific entries or a method for appending to the global whitelist will be required.

It also may make sense to introduce a command line tool for setting the staging specific config to provide a simple workflow.

minimal requirements:

  • staging specific repo-checker-binary-whitelist* settings
  • clear staging specific values on accept of that staging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant