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

Update module metadata #97

Merged
merged 1 commit into from
Aug 21, 2017
Merged

Update module metadata #97

merged 1 commit into from
Aug 21, 2017

Conversation

mcgege
Copy link
Member

@mcgege mcgege commented Jul 4, 2017

Rewrite of metadata.json based on https://docs.puppet.com/puppet/4.10/modules_metadata.html

Signed-off-by: Michael Geiger michael.geiger@telekom.de

@mcgege
Copy link
Member Author

mcgege commented Jul 4, 2017

Maybe we should also include operatingsystem_support, but I'm unsure which distros + versions should be listed ... and also a new version release to the Puppet Forge would be nice :-)

@mcgege
Copy link
Member Author

mcgege commented Jul 19, 2017

@artem-sidorenko @bitvijays What do you think about this?

Copy link
Member

@artem-sidorenko artem-sidorenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mcgege thanks! Regarding operatingsystem_support, here is the similar list from chef-os-hardening. Basically this list represents what we are testing in the CI. As we do not have automated integration tests here yet, not sure what should be there. For me it looks like you did a lot of changes for RHEL, Suse, Ubuntu. So puppet-os-hardening should run there, right?

Regarding the release of puppet-os-hardening, let us review/merge all your PRs first and then push the new release. @bitvijays can you handle the release process to puppet forge? @chris-rock can you add @bitvijays on the puppet forge? Or it should be done by @arlimus ?

@vjeffrey I can't really review it as I do not know the current puppet standards on this. Can you maybe have a look?

@mcgege
Copy link
Member Author

mcgege commented Jul 22, 2017

@artem-sidorenko I can confirm OpenSUSE 42.1 & 42.2, SLES 12, CentOS 7, Ubuntu 14.04 & 16.04. RHEL 7 should also work, as it is similar to CentOS 7. For other distros + versions, we could either implement #79 or guess based on our expirience :-)

@artem-sidorenko
Copy link
Member

@mcgege #79 makes definitely sense, but lets go ahead and not wait for it. You list looks totally okay for me, could you maybe update the PR?

@mcgege
Copy link
Member Author

mcgege commented Jul 26, 2017

@artem-sidorenko Ok, I just added the OS versions

@artem-sidorenko
Copy link
Member

@stefanbethke it would be cool if you could review this one if you like/can

@stefanbethke
Copy link

I agree that listing OSes implies that some validation has taken place that the module will work on those releases. For the time being, I'd only list the ones that can be verified by automated or manual tests, which should be documented.

@artem-sidorenko
Copy link
Member

@stefanbethke right, they are all verified by @mcgege manually as we do not have automated testing here yet (#79), so it should be Okay I think. Can you maybe review the metadata, can we merge this PR?

metadata.json Outdated
"requirements": [
{
"name": "puppet",
"version_requirement": ">= 3.0.0 < 5.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why < 5.0.0?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just checked my agent versions - with the last upgrade on Puppet Enterprise I partly rolled out puppet agent v5, so I think I could raise this to < 6.0.0

{
"operatingsystem": "CentOS",
"operatingsystemrelease": [
"7"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about CentOS 6?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I didn't test it with CentOS 6 ... it should work, but I cannot prove it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Agreed.

metadata.json Outdated
"operatingsystem": "OpenSuSE",
"operatingsystemrelease": [
"13",
"42"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong indentation.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm ... somehow my spaces were converted to a tab ... will correct this :-|

metadata.json Outdated
"operatingsystem": "Ubuntu",
"operatingsystemrelease": [
"14",
"16"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong indentation

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same ...

Rewrite of metadata.json based on https://docs.puppet.com/puppet/4.10/modules_metadata.html

Signed-off-by: Michael Geiger <michael.geiger@telekom.de>
@mcgege
Copy link
Member Author

mcgege commented Aug 21, 2017

@artem-sidorenko How should we proceed here?

@artem-sidorenko
Copy link
Member

Lets merge it, if we face any problems - we should fix them in other PRs

@mcgege thanks for your patience!

We should also release a new version on puppet forge, @chris-rock how can we do that from your POV? Do you have the credentials/access to puppet forge?

@artem-sidorenko artem-sidorenko merged commit 5ad6222 into dev-sec:master Aug 21, 2017
@mcgege mcgege deleted the metadata branch November 8, 2017 07:37
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