-
Story
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
Security Level: Public (Visbile by non-authn users.)
-
None
This story tracks the porting of the YAIM configuration module to puppet. The module will assume a CENTOS 7 deployment for services. The module if possible shouldn't have any dependency on YAIM code.
The module MUST follow best practices and guidelines for puppet, MUST include unit testing and pass linting checks.
Puppet style guide:
https://puppet.com/docs/puppet/5.3/style_guide.html
Puppet lint tool:
SonarQube has a puppet plugin which can also help:
https://github.com/iwarapter/sonar-puppet
And is already used for argus-authz puppet module:
https://sonar.cloud.cnaf.infn.it/overview?id=argus-mw-devel
Some more resources (probably a bit old):
https://puppet.com/blog/writing-great-modules-an-introduction
https://puppet.com/blog/verifying-puppet-checking-syntax-and-writing-automated-tests
https://puppet.com/blog/test-driven-development-puppet
Check also the puppet development kit:
https://puppet.com/docs/pdk/1.x/pdk.html
https://puppet.com/blog/unit-testing-rspec-puppet-for-beginners
A talk giving an introduction on puppet module testing:
https://www.youtube.com/watch?v=GgNrxLfoDF8
- blocks
-
STOR-1071 CENTOS 7 porting
- Closed
- is blocked by
-
STOR-1072 StoRM backend puppet module
- Closed
-
STOR-1073 StoRM Frontend puppet module
- Closed
-
STOR-1074 StoRM Gridftp puppet module
- Closed
-
STOR-1075 StoRM WebDAV puppet module
- Closed
-
STOR-1076 StoRM Info provider puppet module
- Closed
-
STOR-1184 StoRM CDMI puppet module
- Closed
- relates to
-
STOR-1138 Automate the update of storm-puppet-module documentation
- Resolved