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 declarative configuration #163

Open
sambhav opened this issue Sep 14, 2022 · 3 comments
Open

Allow declarative configuration #163

sambhav opened this issue Sep 14, 2022 · 3 comments

Comments

@sambhav
Copy link

sambhav commented Sep 14, 2022

Octopilot looks like an amazing tool. Following the Git-ops ideology, it would be great if it could also support providing all of its command line options through a config file (ideally a YAML file) and it would be even better if it could intake multiple such configuration files and process them in parallel.

@sambhav
Copy link
Author

sambhav commented Sep 14, 2022

I was imagining that the updaters could have proper structured fields in the configuration file, that mimics the updater structs instead of the string parsing that currently happens. This would make it easier to define the updaters. A similar strategy could be applied for the repositories.

@MPV
Copy link
Contributor

MPV commented Sep 14, 2023

@samj1912 Did you end up finding a way to do this with octopilot?
Or if you wound up doing this with some other kind of tool/pattern, would you be open to share your workaround?

@sambhav
Copy link
Author

sambhav commented Sep 14, 2023

Ended up using updatecli which worked a bit better for me as it was declarative and supported GHE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants