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

(MODULES-8393) Add task required metadata, hide extra implementations #353

Merged
merged 2 commits into from Dec 19, 2018

Conversation

MikaelSmith
Copy link
Contributor

@MikaelSmith MikaelSmith commented Dec 19, 2018

Adds task metadata required to publish to the Forge. Also declare
input_method where it would use the default both and hide extra
implementations for task runners that implement private tasks and task
implementations.

@branan
Copy link
Contributor

branan commented Dec 19, 2018

Would be nice to see in the commit message that this is related to task metadata, since this module has been published to the forge for years.

Adds task metadata required to publish to the Forge. Also declare
input_method where it would use the default `both` and hide extra
implementations for task runners that implement private tasks and task
implementations.
@MikaelSmith MikaelSmith changed the title (MODULES-8393) Add required metadata, hide extra implementations (MODULES-8393) Add task required metadata, hide extra implementations Dec 19, 2018
@MikaelSmith
Copy link
Contributor Author

Done. Shipping to the forge with the current set of tasks would've failed because the forge requires that every task has a metadata file.

@branan
Copy link
Contributor

branan commented Dec 19, 2018

I'd like someone who actually knows what task metadata looks like to approve this, but nothing jumps out to me as evil 👍

@MikaelSmith
Copy link
Contributor Author

Looks like Ruby pre-2.3 may be borked.

@MikaelSmith
Copy link
Contributor Author

Should I drop gem update --system, or the old Puppet versions?

@branan
Copy link
Contributor

branan commented Dec 19, 2018

We want this module to maintain support for Puppet 4, even in the master branch, so that lagging users can continue to use it to update. I believe the gem update --system was added to work around a bug in Travis, so I'm not sure we can drop that.

@branan
Copy link
Contributor

branan commented Dec 19, 2018

In other words, I have NFI what to do here. I'm fine merging this over the red, since it's just a metadata change. We'll have to work out the travis mess separately as part of readying this for a 2.0 release

Ruby before 2.3 is no longer maintained, drop testing Ruby versions that
are EOL. Also add testing with Puppet 6.
@MikaelSmith
Copy link
Contributor Author

Trying testing with Puppet 4 + Ruby 2.3. Not ideal, but better than red tests.

@MikaelSmith
Copy link
Contributor Author

Worked. I'll get someone from my team to review as well.

@adreyer adreyer merged commit eece6ae into puppetlabs:master Dec 19, 2018
@MikaelSmith MikaelSmith deleted the MODULES-8393 branch December 19, 2018 21:53
@puppetcla
Copy link

CLA signed by all contributors.

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

4 participants