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

(enhancement) 'Enabled' is missing for job definition #164

Open
PietjePu opened this issue Oct 14, 2021 · 4 comments
Open

(enhancement) 'Enabled' is missing for job definition #164

PietjePu opened this issue Oct 14, 2021 · 4 comments
Labels
good first issue Good for newcomers

Comments

@PietjePu
Copy link

I succesfully put our bacula configuration in puppet the past couple of weeks and very pleased how the module works, but because we have old jobs which are only there for restore-purposes we need the 'Enabled = yes|no' option for job definitions.

Is it possible to include it? I can add it manually, but that will break when I update the module...

Thanks in advance!

@smortex smortex added the good first issue Good for newcomers label Oct 14, 2021
@smortex
Copy link
Member

smortex commented Oct 14, 2021

Hey @PietjePu!

Have you considered opening a Pull Request (PR) to add your change 😉? This look like a perfect enhancement for a first-time contributor!

If you do not know how to start, here is a quite complete guide about the process of contributing to projects on GitHub:
https://www.dataschool.io/how-to-contribute-on-github/

In any case, do not feel scared: we are here to help!

@PietjePu
Copy link
Author

Thanks! As you guessed I don't have any experience regarding contributing to projects. Apart from the 'job enabled'-option, I'm missing autochanger configuration as well. Will that be something useful to add as well? Or is there a reason it's not included? I'm happy to add it and share the code...

@smortex
Copy link
Member

smortex commented Oct 15, 2021

The goal for a module is to benefit to the most people, so if you have the usage of the autocharger and can contribute it, we will be happy to merge it! We try to keep the test suite in good shape to ensure the code does not break.

I would recommend you start with adding 'Enabled' which will have less "moving pieces" and will still make you interact with multiple main aspects of contributing to Free Software: try to implement and test the changes on your machine, when ready (or if you are blocked) open a PR. We will then guide you to add tests to ensure your new feature is not broken in the future.

Thanks!

@PietjePu
Copy link
Author

You're right. I'll start with the enabled setting. For now I included everything (including the autochanger configuration) in my local copy of the module (seems to work OK, but you never know), because I need the functionality on a short notice. When everything is OK I'll get back and open a pr for the enabled-setting! Thanks so far!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants