cirrax-gitolite-1.3.30040755000175000017500000000000013572015405011533 5ustar00cirrax-gitolite-1.3.3/.puppet-lint.rc0100644000175000017500000000001313521543232014464 0ustar00--relative cirrax-gitolite-1.3.3/.sync.yml0100644000175000017500000000014413572015010013353 0ustar00 .travis.yml: simplecov: true spec/spec_helper.rb: coverage_report: true mock_with: ':rspec' cirrax-gitolite-1.3.3/LICENSE0100644000175000017500000010451313325601464012622 0ustar00 GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read . cirrax-gitolite-1.3.3/README.md0100644000175000017500000000570113572015010013061 0ustar00# gitolite puppet module [![Build Status](https://travis-ci.org/cirrax/puppet-gitolite.svg?branch=master)](https://travis-ci.org/cirrax/puppet-gitolite) [![Puppet Forge](https://img.shields.io/puppetforge/v/cirrax/gitolite.svg?style=flat-square)](https://forge.puppetlabs.com/cirrax/gitolite) [![Puppet Forge](https://img.shields.io/puppetforge/dt/cirrax/gitolite.svg?style=flat-square)](https://forge.puppet.com/cirrax/gitolite) [![Puppet Forge](https://img.shields.io/puppetforge/e/cirrax/gitolite.svg?style=flat-square)](https://forge.puppet.com/cirrax/gitolite) [![Puppet Forge](https://img.shields.io/puppetforge/f/cirrax/gitolite.svg?style=flat-square)](https://forge.puppet.com/cirrax/gitolite) #### Table of Contents 1. [Overview](#overview) 1. [Usage](#usage) 1. [Reference](#reference) 1. [Contribuiting](#contributing) ## Overview This module is used to configure gitolite and to configure git repositories and permissions. ## Usage To start using gitolite you need to include the gitolite main class. A minimal example might be: ~~~ class{'gitolite': user => 'gitolite', userhome => '/srv/gitolite', } ~~~ The gitolite::admin class is only used if you like to do all admin work through puppet (like create new repos, users and permissions). If gitolite::admin is not included, you can use the admin git repo to do these tasks (feature of gitolite). ## Reference Find documentation about possible parameters on top of each manifest. Also see [REFERENCE.md](REFERENCE.md) ### classes #### gitolite The main class to install and configure gitolite. #### gitolite::admin This class manages the gitolite.conf file and prepares to manage the ssh keys with puppet. Use this class if you want to do all admin work through puppet (add users, repositories and permissions) do not use this class if you want to use the gitolite-admin.git repositoy for these tasks. (you have been warned ! if you use it once, there is no puppet way back, only manual work will get you back) #### gitolite::client Install the git package. #### gitolite::ssh_key Generate an SSH authentication key for authentication to a remote system (eg. for git hooks). #### gitolite::params System specific parameters. ### defined types #### gitolite::repo Define git repositories #### gitolite::repos Define several git repositories with merged default values. #### gitolite::user This resources defines a git user #### gitolite::users Define several git users with merged default values. ## Contributing Please report bugs and feature request using GitHub issue tracker. For pull requests, it is very much appreciated to check your Puppet manifest with puppet-lint and the available spec tests in order to follow the recommended Puppet style guidelines from the Puppet Labs style guide. ### Authors This module is mainly written by [Cirrax GmbH](https://cirrax.com). See the [list of contributors](https://github.com/cirrax/puppet-gitolite/graphs/contributors) for a list of all contributors. cirrax-gitolite-1.3.3/REFERENCE.md0100644000175000017500000002635413572015010013431 0ustar00# Reference ## Table of Contents **Classes** * [`gitolite`](#gitolite): This class is inherited by setup.pp and admin.pp It's intention is to have alle the config parameters. If you only use this class (and the * [`gitolite::admin`](#gitoliteadmin): This class manages the gitolite.conf file and prepares to manage the ssh keys with puppet. do not use this class if you want to use the gito * [`gitolite::client`](#gitoliteclient): Class to install git * [`gitolite::ssh_key`](#gitolitessh_key): Generate an SSH authentication key Key generation for (passwordless) authentication to a remote system. **Defined types** * [`gitolite::repo`](#gitoliterepo): this resources defines a git repository you also can use it to define values for a group of repositories (by using an @ in front of the group * [`gitolite::repos`](#gitoliterepos): this resource defines a group of repos with defaults * [`gitolite::user`](#gitoliteuser): this resources defines a git user you also can use it to define values for a group of repositories (by using an @ in front of the group name) * [`gitolite::users`](#gitoliteusers): this resource defines a group of users with defaults **Resource types** * [`gitremote`](#gitremote): add a remote to a git repository ## Classes ### gitolite This class is inherited by setup.pp and admin.pp It's intention is to have alle the config parameters. If you only use this class (and the setup), you can still do all admin work (manage users, permissions etc. throug the git repository gitolite-admin.git.) #### Parameters The following parameters are available in the `gitolite` class. ##### `reporoot` Data type: `String` path to the directory where you will store the repositories. This does not have to be equal to the $users home directory. defaults to $userhome Default value: "${userhome}/repositories" ##### `user` Data type: `String` the user to host the git repositories this user needs a home directory to work with gitolite. ##### `userhome` Data type: `String` the home directory of the user ##### `user_ensure` Data type: `Boolean` if true, $user will be created, if false, you have to create the user with the homedirectory elsewhere. defaults to true Default value: `true` ##### `umask` Data type: `String` see the rc file docs for how/why you might change this defaults to '0077' which gives perms of '0700' Default value: '0077' ##### `git_config_keys` Data type: `String` look for "git-config" in the documentation default: '.*' Default value: '.*' ##### `log_extra` Data type: `Boolean` set to true for extra log details default: false Default value: `false` ##### `log_dest` Data type: `Array` array of log destinations. available values are: normal: normal gitolite logs syslog: log to syslog repo-log: log just the update records to gl-log in the bare repo directory defaults to ['normal'] Default value: ['normal'] ##### `roles` Data type: `Array` Array of roles to add. default: ['READERS', 'WRITERS'] Default value: ['READERS', 'WRITERS'] ##### `site_info` Data type: `Boolean` the 'info' command prints this as additional info default to false Default value: `false` ##### `gitolite_hostname` Data type: `String` the hostname, to unset, set to false defaults to $::hostname Default value: $::hostname ##### `local_code` Data type: `String` suggested locations for site-local gitolite code defaults to '', no site-local code Default value: '' ##### `additional_gitoliterc` Data type: `Hash` hash of additional lines to add on gitolite.rc file defaults to empty (beware of "' etc ...) example: { 'CACHE' => '"Redis"' } Default value: {} ##### `commands` Data type: `Array` Array of commands and features to enable defaults to ['help', 'desc', 'info', 'perms' ] Default value: [ 'help', 'desc', 'info', 'perms', 'writable', 'ssh-authkeys', 'git-config', 'daemon', 'gitweb', ] ##### `package_ensure` Data type: `String` howto ensure the packages to install Default value: 'present' ##### `packages` Data type: `Array` packages to install for gitolite Default value: [] ##### `additional_packages` Data type: `Array` any additional packages you like to install Default value: [] ##### `admin_key_source` Data type: `String` provide a admin key source (default to false) Default value: '' ##### `admin_key` Data type: `String` admin key (string) (default to false) Default value: '' ##### `additional_gitoliterc_notrc` Data type: `Hash` hash of additional lines to add on gitolite.rc file after the rc vars defaults to empty (beware of "' etc ...) example: { '$REF_OR_FILENAME_PATT' => 'qr(^[0-9a-zA-Z][-0-9a-zA-Z._\@/+ :%,]*$)' } Default value: {} ##### `fetch_cron` Data type: `Boolean` if a cronjob should be established to fetch from remote repos defaults to false Default value: `false` ### gitolite::admin This class manages the gitolite.conf file and prepares to manage the ssh keys with puppet. do not use this class if you want to use the gitolite-admin.git repositoy for these tasks. (you have been warned ! if you use it once, there is no puppet way back, only manual work will get you back) #### Parameters The following parameters are available in the `gitolite::admin` class. ##### `remove_admin_repo` Data type: `Boolean` if true (the default) the repository gitoline_admin.git will be removed Default value: `true` ##### `repos` Data type: `Hash` a hash of repos, to be defined Default value: {} ##### `users` Data type: `Hash` a hash of users, to be defined Default value: {} ##### `add_testing_repo` Data type: `Boolean` allow RW+ for all users to the testing repo default: true Default value: `true` ### gitolite::client Class to install git ### gitolite::ssh_key Generate an SSH authentication key Key generation for (passwordless) authentication to a remote system. #### Parameters The following parameters are available in the `gitolite::ssh_key` class. ##### `filename` Data type: `String` Filename (full path) for the key. Required. ##### `type` Data type: `String` Type of key, either dsa, ecdsa or rsa. Defaults to rsa. Default value: 'rsa' ##### `length` Data type: `Integer` Key length. Defaults to 2048. See man ssh-keygen for restrictions regarding non RSA keys. Default value: 2048 ##### `password` Data type: `String` Password for the key. Defaults to no password. This is not very secure as the password is visible in plain text in the puppet manifest and as a process parameters when creating the key. Default value: '' ##### `comment` Data type: `String` Comment describing the Key. Defaults to "Automatic authentication key for $user on $fqdn". Default value: 'undef' ##### `user` Data type: `String` User who uses this key. This user must have write access to the directory containing the key. Defaults to "root" Default value: 'root' ## Defined types ### gitolite::repo this resources defines a git repository you also can use it to define values for a group of repositories (by using an @ in front of the group name) #### Parameters The following parameters are available in the `gitolite::repo` defined type. ##### `repos` Data type: `Array` an array of repos (or a group of repos ( @blah ) defaults to [ $title ] Default value: [$title] ##### `comments` Data type: `Variant[String, Array]` an array of comments to add defaults to [] Default value: [] ##### `rules` Data type: `Hash` an array of rules. a rule has three elements: permission, refex and user/group a hash of permissions: [{ 'RW+' => 'username'}, ... ] Default value: {} ##### `options` Data type: `Hash` Default value: {} ##### `configs` Data type: `Hash` Default value: {} ##### `add_configs` Data type: `Hash` additional configs, merged with configs Default value: {} ##### `groups` Data type: `Array` an array of groups to append the repos to the group names can be prefix with an @ sign (if they are puppet take care of) Default value: [] ##### `order` Data type: `String` string, to order the repos $order will be prefixed with 60 for the grouping section and 90 for the repo section. defaults to '' Default value: '' ##### `description` Data type: `String` a description to add to the repo Default value: '' ##### `hooks` Data type: `Hash` hooks to install Default value: {} ##### `group` Data type: `String` Default value: 'root' ##### `remotes` Data type: `Hash` Hash of remote repos to sync branches and tags from defaults to {} Example: 'upstream' => { 'url' => 'https://github.com/openstack/puppet-nova' 'fetches' => [ 'master:master', 'refs/tags/*:refs/tags/*', 'refs/heads/stable/*:refs/heads/stable/*', ] } will update the master branch, all tags and all branches stable/* from the remote location mentioned in url. To remove an upstrem you can set ensure to 'absent' You can set more than one repo to sync from, but it's up to you to ensure that no conflicts occur ! Default value: {} ### gitolite::repos this resource defines a group of repos with defaults #### Parameters The following parameters are available in the `gitolite::repos` defined type. ##### `defaults` Data type: `Hash` defaults for all generated repos Default value: {} ##### `repos` Data type: `Hash` repos to create see gitolite::repo for parameters Default value: {} ### gitolite::user this resources defines a git user you also can use it to define values for a group of repositories (by using an @ in front of the group name) #### Parameters The following parameters are available in the `gitolite::user` defined type. ##### `user` Data type: `String` the user name defaults to $title Default value: $title ##### `keys` Data type: `Array` array of users ssh keys Default value: [] ##### `key_source` Data type: `String` a puppet source to fetch key from Default value: '' ##### `comments` Data type: `Variant[Array, String]` an array of comments to add to this section defaults to [] Default value: [] ##### `groups` Data type: `Array` an array of groups to append the user to the group names can be prefix with an @ sign (if they are puppet take care of) defaults to [] Default value: [] ##### `order` Data type: `String` string, to order the repos $order will be prefixed with 30 for the grouping section and 20 for the user section. defaults to '' Default value: '' ### gitolite::users this resource defines a group of users with defaults #### Parameters The following parameters are available in the `gitolite::users` defined type. ##### `defaults` Data type: `Hash` defaults for all generated users Default value: {} ##### `users` Data type: `Hash` users to create see gitolite::user for parameters Default value: {} ## Resource types ### gitremote add a remote to a git repository #### Properties The following properties are available in the `gitremote` type. ##### `ensure` Valid values: present, absent The basic property that the resource should be in. Default value: present ##### `url` the url of the remote repository ##### `fetches` Array of fetch definitions #### Parameters The following parameters are available in the `gitremote` type. ##### `name` namevar the title ##### `remotename` the name of the remote to create ##### `directory` the the directory the repository is ##### `confowner` the the owner of the config file cirrax-gitolite-1.3.3/data0040755000175000017500000000000013572015405012444 5ustar00cirrax-gitolite-1.3.3/data/Debian-family.yaml0100644000175000017500000000012013522554276016047 0ustar00--- # module: gitolite, Debian-family.yaml gitolite::packages: - 'gitolite3' cirrax-gitolite-1.3.3/hiera.yaml0100644000175000017500000000024013521543232013555 0ustar00--- version: 5 defaults: datadir: 'data' data_hash: 'yaml_data' hierarchy: - name: 'Operating System Family' path: '%{facts.os.family}-family.yaml' cirrax-gitolite-1.3.3/lib0040755000175000017500000000000013572015405012301 5ustar00cirrax-gitolite-1.3.3/lib/puppet0040755000175000017500000000000013572015405013616 5ustar00cirrax-gitolite-1.3.3/lib/puppet/provider0040755000175000017500000000000013572015405015450 5ustar00cirrax-gitolite-1.3.3/lib/puppet/provider/gitremote0040755000175000017500000000000013572015405017447 5ustar00cirrax-gitolite-1.3.3/lib/puppet/provider/gitremote/ruby.rb0100644000175000017500000000441613521543356021043 0ustar00 Puppet::Type.type(:gitremote).provide(:ruby) do desc 'gitclone for posix' commands gitcommand: 'git', chowncommand: 'chown' def create # initialy add the git remote gitcommand '-C', resource[:directory], 'remote', 'add', resource[:remotename], resource[:url] # now we need to set the correct fetchers begin (gitcommand '-C', resource[:directory], 'config', '--unset-all', 'remote.' + resource[:remotename] + '.fetch') rescue Puppet::ExecutionFailure [] end resource[:fetches].each do |fetch| (gitcommand '-C', resource[:directory], 'config', '--add', 'remote.' + resource[:remotename] + '.fetch', fetch) end chowncommand resource[:confowner], resource[:directory] + '/config' end def destroy # remove the git remote gitcommand '-C', resource[:directory], 'remote', 'remove', resource[:remotename] chowncommand resource[:confowner], resource[:directory] + '/config' end def exists? # check if the remote already exists (gitcommand '-C', resource[:directory], 'remote', 'show', '-n').split("\n").include?(resource[:remotename]) end def url # the ’getter’ # return the current url of remote, without newline (gitcommand '-C', resource[:directory], 'remote', 'get-url', resource[:remotename]).delete("\n") end def url=(_value) # the ’setter’ # the correct the remote url gitcommand '-C', resource[:directory], 'remote', 'set-url', resource[:remotename], resource[:url] chowncommand resource[:confowner], resource[:directory] + '/config' end def fetches # the ’getter’ # return the current fetches (gitcommand '-C', resource[:directory], 'config', '--get-all', 'remote.' + resource[:remotename] + '.fetch').split("\n") rescue Puppet::ExecutionFailure [] end def fetches=(_value) # the ’setter’ # set the fetches begin (gitcommand '-C', resource[:directory], 'config', '--unset-all', 'remote.' + resource[:remotename] + '.fetch') rescue Puppet::ExecutionFailure [] end resource[:fetches].each do |fetch| (gitcommand '-C', resource[:directory], 'config', '--add', 'remote.' + resource[:remotename] + '.fetch', fetch) end chowncommand resource[:confowner], resource[:directory] + '/config' end end cirrax-gitolite-1.3.3/lib/puppet/type0040755000175000017500000000000013572015405014577 5ustar00cirrax-gitolite-1.3.3/lib/puppet/type/gitremote.rb0100644000175000017500000000113313521543232017173 0ustar00 Puppet::Type.newtype(:gitremote) do @doc = 'add a remote to a git repository' ensurable # parameters: change the way how the provider work newparam(:name) do desc 'the title' end newparam(:remotename) do desc 'the name of the remote to create' end newparam(:directory) do desc 'the the directory the repository is' end newparam(:confowner) do desc 'the the owner of the config file' end newproperty(:url) do desc 'the url of the remote repository' end newproperty(:fetches, array_matching: :all) do desc 'Array of fetch definitions' end end cirrax-gitolite-1.3.3/manifests0040755000175000017500000000000013572015405013524 5ustar00cirrax-gitolite-1.3.3/manifests/admin.pp0100644000175000017500000000605213572015010015224 0ustar00# # This class manages the gitolite.conf file # and prepares to manage the ssh keys with puppet. # # do not use this class if you want to use the # gitolite-admin.git repositoy for these tasks. # (you have been warned ! if you use it once, # there is no puppet way back, only manual work # will get you back) # # @param remove_admin_repo # if true (the default) the repository # gitoline_admin.git will be removed # @param repos # a hash of repos, to be defined # @param users # a hash of users, to be defined # @param add_testing_repo # allow RW+ for all users to the testing repo # default: true # class gitolite::admin ( Boolean $remove_admin_repo = true, Hash $repos = {}, Hash $users = {}, Boolean $add_testing_repo = true, ) inherits gitolite { concat { $::gitolite::conffile: ensure => present, notify => $::gitolite::exec_update, } $h = '#####################' $default_fragments = { 'gitolite_conf_main_header' => { 'content' => "${h}\n# managed with puppet\n\n", 'order' => '00', }, 'gitolite_conf_user_group_header' => { 'content' => "${h}\n# users group section\n\n", 'order' => '30', }, 'gitolite_conf_repo_group_header' => { 'content' => "${h}\n# repos group section\n\n", 'order' => '50', }, 'gitolite_conf_repo_header' => { 'content' => "${h}\n# repo section\n\n", 'order' => '80', }, } ensure_resources('concat::fragment', $default_fragments, {'target' => $::gitolite::conffile }) # manage the keydir: file{ "${::gitolite::userhome}/.puppet_userkeys": ensure => directory, force => true, recurse => true, purge => true, notify => Exec['gitolite update user keys from source'], } $gh=$::gitolite::userhome exec{'gitolite update user keys from source': command => "/bin/true ; rm -rf ${gh}/.puppet_userkeys2 ; find ${gh}/.puppet_userkeys -type d|sed 's|/\\.puppet_userkeys|/.puppet_userkeys2|'|xargs mkdir ; (cd ${gh}/.puppet_userkeys; find -type f -exec split -l 1 -a 3 -d --additional-suffix=.pub {} ../.puppet_userkeys2/{}@ \\; ) ; ", refreshonly => true, before => File[ $gitolite::keydir ], require => File[ "${::gitolite::userhome}/.puppet_userkeys" ], } file{ $::gitolite::keydir: ensure => directory, force => true, recurse => true, purge => true, source => "${::gitolite::userhome}/.puppet_userkeys2", notify => $::gitolite::exec_update, } # remove the admin repo since it is not used: if $remove_admin_repo { file {"${gitolite::reporoot}/gitolite-admin.git": ensure => absent, force => true, backup => false, # if you used it, you have this localy available, otherwise it's the default ! } } # add testing repo if $add_testing_repo { gitolite::repo{'testing': rules => { 'RW+' => '@all' }, comments => ['default for testing repo'], } } # ensure some resources ensure_resources('gitolite::repo', $repos) ensure_resources('gitolite::user', $users) } cirrax-gitolite-1.3.3/manifests/client.pp0100644000175000017500000000012513572015010015405 0ustar00# # Class to install git # # class gitolite::client { ensure_packages(['git']) } cirrax-gitolite-1.3.3/manifests/init.pp0100644000175000017500000001644413572015010015105 0ustar00# This class is inherited by setup.pp and admin.pp # # It's intention is to have alle the config parameters. # # If you only use this class (and the setup), you can still do all admin work # (manage users, permissions etc. throug the git repository # gitolite-admin.git.) # # @param reporoot # path to the directory where you will store the repositories. # This does not have to be equal to the $users home directory. # defaults to $userhome # @param user # the user to host the git repositories # this user needs a home directory to work with gitolite. # @param userhome # the home directory of the user # @param user_ensure # if true, $user will be created, if false, you have # to create the user with the homedirectory elsewhere. # defaults to true # @param umask # see the rc file docs for how/why you might change this # defaults to '0077' which gives perms of '0700' # @param git_config_keys # look for "git-config" in the documentation # default: '.*' # @param log_extra # set to true for extra log details # default: false # @param log_dest # array of log destinations. # available values are: # normal: normal gitolite logs # syslog: log to syslog # repo-log: log just the update records to # gl-log in the bare repo directory # defaults to ['normal'] # @param roles # Array of roles to add. # default: ['READERS', 'WRITERS'] # @param site_info # the 'info' command prints this as additional info # default to false # @param gitolite_hostname # the hostname, to unset, set to false # defaults to $::hostname # @param local_code # suggested locations for site-local gitolite code # defaults to '', no site-local code # @param additional_gitoliterc # hash of additional lines to add on gitolite.rc file # defaults to empty (beware of "' etc ...) # example: # { 'CACHE' => '"Redis"' } # @param commands # Array of commands and features to enable # defaults to ['help', 'desc', 'info', 'perms' ] # @param package_ensure # howto ensure the packages to install # @param packages # packages to install for gitolite # @param additional_packages # any additional packages you like to install # @param admin_key_source # provide a admin key source (default to false) # @param admin_key # admin key (string) (default to false) # @param additional_gitoliterc_notrc # hash of additional lines to add on gitolite.rc file # after the rc vars # defaults to empty (beware of "' etc ...) # example: # { '$REF_OR_FILENAME_PATT' => 'qr(^[0-9a-zA-Z][-0-9a-zA-Z._\@/+ :%,]*$)' } # @param fetch_cron # if a cronjob should be established to fetch from remote repos # defaults to false # class gitolite ( String $user, String $userhome, String $reporoot = "${userhome}/repositories", Boolean $user_ensure = true, String $umask = '0077', String $git_config_keys = '.*', Boolean $log_extra = false, Array $log_dest = ['normal'], Array $roles = ['READERS', 'WRITERS'], Boolean $site_info = false, String $gitolite_hostname = $::hostname, String $local_code = '', Hash $additional_gitoliterc = {}, Hash $additional_gitoliterc_notrc = {}, Array $commands = [ 'help', 'desc', 'info', 'perms', 'writable', 'ssh-authkeys', 'git-config', 'daemon', 'gitweb', ], String $package_ensure = 'present', Array $packages = [], Array $additional_packages = [], String $admin_key_source = '', String $admin_key = '', Boolean $fetch_cron = false, ) { Exec['gitolite_compile'] -> File <| tag == 'gitolite-repo' |> ensure_packages($::gitolite::additional_packages) package{ $packages : ensure => $::gitolite::package_ensure, tag => 'gitolite', } #contain ::gitolite::setup if $user_ensure { user{$user: ensure => present, comment => 'gitolite user', home => $userhome, managehome => true, system => true, before => Exec['gitolite_setup'], } # create an ssh key for gitolite user file { "${userhome}/.ssh": ensure => directory, owner => $user, group => $user, mode => '0700', require => User[$user], } class{'::gitolite::ssh_key': filename => "${userhome}/.ssh/id_ed25519", type => 'ed25519', user => $user, require => File["${userhome}/.ssh"], } } Exec { path => ['/usr/bin', '/usr/sbin', '/bin'], } exec{'gitolite_setup': command => "su ${gitolite::user} -c 'gitolite setup -a dummy; mkdir ~/.gitolite/keydir'", unless => "test -d ~${user}/.gitolite", creates => "${userhome}/.gitolite", require => Package[$packages], } -> exec{'gitolite_compile': command => "su ${gitolite::user} -c 'gitolite compile'", refreshonly => true, } -> exec{'gitolite_trigger_post_compile': command => "su ${gitolite::user} -c 'gitolite trigger POST_COMPILE'", refreshonly => true, } if "${userhome}/repositories" != $reporoot { file{ $reporoot: ensure => directory, owner => $user, mode => '0700', } -> exec{'gitolite: move repositories': command => "mv ${userhome}/repositories/* ${reporoot}/; true", unless => [ "test -h ${userhome}/repositories", # symplink ? ], } # if linkpath is not a sym -> exec{'gitolite: remove repositories directory': command => "rmdir ${userhome}/repositories;ln -sf ${reporoot} ${userhome}/repositories", unless => [ "test -h ${userhome}/repositories", # symlink ? "test \"`readlink ${userhome}/repositories`\" == '${reporoot}'", # symlink to target ? ], } } file{"${userhome}/.gitolite.rc": content => template('gitolite/gitolite.rc.erb'), mode => '0700', owner => $user, notify => Exec['gitolite_compile', 'gitolite_trigger_post_compile'], } $conffile = "${gitolite::userhome}/.gitolite/conf/gitolite.conf" $keydir = "${gitolite::userhome}/.gitolite/keydir" $exec_update = Exec['gitolite_compile', 'gitolite_trigger_post_compile'] # manage initial key, if provided if $admin_key_source != '' { file { "${keydir}/admin@init0.pub": source => $admin_key_source, notify => $exec_update, } } if $admin_key != '' { file { "${keydir}/admin@init1.pub": content => $admin_key, notify => $exec_update, } } file{"${userhome}/scripts": ensure => directory, mode => '0755', owner => $user, } concat{ "${userhome}/upgrade-repos.sh": owner => 'root', group => 'root', mode => '0700', } concat::fragment{ "${userhome}/upgrade-repos.sh header": target => "${userhome}/upgrade-repos.sh", content => "#!/bin/sh\n#managed with puppet (module gitolite)\n\n", order => '00', } if $fetch_cron { cron{'fetch gitolite repos upstream': command => "${userhome}/upgrade-repos.sh", user => 'root', hour => fqdn_rand(4, 'gitolite'), minute => fqdn_rand(60, 'gitolite'), } } else { cron{'fetch gitolite repos upstream': ensure => 'absent', } } } cirrax-gitolite-1.3.3/manifests/repo.pp0100644000175000017500000001004313572015010015074 0ustar00# # this resources defines a git repository # you also can use it to define values for a group of # repositories (by using an @ in front of the group name) # # @param repos # an array of repos (or a group of repos ( @blah ) # defaults to [ $title ] # @param comments # an array of comments to add defaults to [] # @param rules # an array of rules. # a rule has three elements: # permission, refex and user/group # a hash of permissions: # [{ 'RW+' => 'username'}, ... ] # @param options # @param configs # @param add_configs # additional configs, merged with configs # @param groups # an array of groups to append the repos to # the group names can be prefix with an @ sign # (if they are puppet take care of) # @param order # string, to order the repos # $order will be prefixed with 60 for the grouping section # and 90 for the repo section. # defaults to '' # @param description # a description to add to the repo # @param hooks # hooks to install # @param group # @param remotes # Hash of remote repos to sync branches and tags from # defaults to {} # Example: # 'upstream' => { # 'url' => 'https://github.com/openstack/puppet-nova' # 'fetches' => [ # 'master:master', # 'refs/tags/*:refs/tags/*', # 'refs/heads/stable/*:refs/heads/stable/*', # ] # } # will update the master branch, all tags and all branches stable/* # from the remote location mentioned in url. # # To remove an upstrem you can set ensure to 'absent' # You can set more than one repo to sync from, but it's up to you # to ensure that no conflicts occur ! # # define gitolite::repo ( Array $repos = [$title], Variant[String, Array] $comments = [], Hash $rules = {}, Hash $options = {}, Hash $configs = {}, Hash $add_configs = {}, Array $groups = [], String $order = '', String $description = '', Hash $hooks = {}, String $group = 'root', Hash $remotes = {}, ) { include ::gitolite concat::fragment { "gitolite_conffile repo ${title}": target => $::gitolite::conffile, content => template('gitolite/repo.erb'), order => "90${order}", } if $groups != [] { $members = $repos concat::fragment { "gitolite_conffile groups (repo) ${title}": target => $::gitolite::conffile, content => template('gitolite/groups.erb'), order => "60${order}", } } if $description != '' { file { "${gitolite::reporoot}/${title}.git/description": content => $description, owner => $gitolite::user, group => $group, tag => ['gitolite-repo'], } } file { "${gitolite::reporoot}/${title}.git/hooks": ensure => 'directory', mode => '0700', owner => $gitolite::user, group => $group, purge => true, recurse => true, tag => ['gitolite-repo'], } # ensure that the gitolite hook is not overwritten. file { "${gitolite::reporoot}/${title}.git/hooks/update": ensure => 'link', target => "${gitolite::userhome}/.gitolite/hooks/common/update", owner => $gitolite::user, group => $group, } $hooks.each | $hname, $dest | { file { "${gitolite::reporoot}/${title}.git/hooks/${hname}": ensure => 'link', target => "${gitolite::userhome}/scripts/${dest}", owner => $gitolite::user, group => $group, } } $remotes.each | $thename, $rem | { gitremote{"remote for ${title} ${thename}": ensure => pick($rem['ensure'], 'present'), remotename => $thename, directory => "${gitolite::reporoot}/${title}.git", confowner => $gitolite::user, url => $rem['url'], fetches => $rem['fetches'], } if pick($rem['ensure'], 'present') != 'absent' { concat::fragment{ "gitolite upgrade-repos.sh: ${title} ${$thename}": target => "${gitolite::userhome}/upgrade-repos.sh", content => "su ${gitolite::user} -c 'git -C ${gitolite::reporoot}/${title}.git fetch ${thename}'\n", order => md5("${title}_${thename}"), } } } } cirrax-gitolite-1.3.3/manifests/repos.pp0100644000175000017500000000050113572015010015255 0ustar00# # this resource defines a group of repos with defaults # # @param defaults # defaults for all generated repos # @param repos # repos to create see gitolite::repo for parameters # define gitolite::repos ( Hash $defaults = {}, Hash $repos = {}, ) { ensure_resources('gitolite::repo', $repos, $defaults) } cirrax-gitolite-1.3.3/manifests/ssh_key.pp0100644000175000017500000000260313572015010015577 0ustar00# # Generate an SSH authentication key # # Key generation for (passwordless) authentication to a # remote system. # # @param filename # Filename (full path) for the key. Required. # @param type # Type of key, either dsa, ecdsa or rsa. Defaults to rsa. # @param length # Key length. Defaults to 2048. See man ssh-keygen for restrictions # regarding non RSA keys. # @param password # Password for the key. Defaults to no password. This is not very secure # as the password is visible in plain text in the puppet manifest and as a # process parameters when creating the key. # @param comment # Comment describing the Key. Defaults to "Automatic authentication key for $user on $fqdn". # @param user # User who uses this key. This user must have write access to the directory # containing the key. Defaults to "root" # class gitolite::ssh_key( String $filename, String $type = 'rsa', Integer $length = 2048, String $password = '', String $comment = 'undef', String $user = 'root', ) { if $comment == 'undef' { $_comment = "Automatic authentication key for ${user} on ${::fqdn}" } else { $_comment = $comment } exec {'key for gitolite': path => ['/usr/bin', '/usr/sbin', '/bin'], command => "ssh-keygen -t ${type} -b ${length} -C \"${_comment}\" -f ${filename} -q -N \"${password}\"", user => $user, creates => $filename, } } cirrax-gitolite-1.3.3/manifests/user.pp0100644000175000017500000000316713572015010015116 0ustar00# # this resources defines a git user # you also can use it to define values for a group of # repositories (by using an @ in front of the group name) # # @param user # the user name # defaults to $title # @param keys # array of users ssh keys # @param key_source # a puppet source to fetch key from # @param comments # an array of comments to add to this section # defaults to [] # @param groups # an array of groups to append the user to # the group names can be prefix with an @ sign # (if they are puppet take care of) # defaults to [] # @param order # string, to order the repos # $order will be prefixed with 30 for the grouping section # and 20 for the user section. # defaults to '' # define gitolite::user ( String $user = $title, Array $keys = [], String $key_source = '', Array $groups = [], Variant[Array, String] $comments = [], String $order = '', ){ include ::gitolite # create the key from source (only one key currently ...) if $key_source != '' { file { "${::gitolite::userhome}/.puppet_userkeys/${user}": source => $key_source, notify => Exec['gitolite update user keys from source' ], } } # create the keys from the keys array $keys.each | $k, $key | { file { "${::gitolite::keydir}/${user}@${k}.pub": content => $key, notify => $::gitolite::exec_update, } } if $groups != [] { $members = $user concat::fragment { "gitolite_conffile groups (user) ${title}": target => $::gitolite::conffile, content => template('gitolite/groups.erb'), order => "40${order}", } } } cirrax-gitolite-1.3.3/manifests/users.pp0100644000175000017500000000050113572015010015266 0ustar00# # this resource defines a group of users with defaults # # @param defaults # defaults for all generated users # @param users # users to create see gitolite::user for parameters # define gitolite::users ( Hash $defaults = {}, Hash $users = {}, ) { ensure_resources('gitolite::user', $users, $defaults) } cirrax-gitolite-1.3.3/metadata.json0100644000175000017500000000214313572015130014255 0ustar00{ "name": "cirrax-gitolite", "version": "1.3.3", "author": "Cirrax GmbH", "summary": "A module to configure gitolite", "license": "GPL-3.0", "source": "https://github.com/cirrax/puppet-gitolite", "project_page": "https://github.com/cirrax/puppet-gitolite", "issues_url": "https://github.com/cirrax/puppet-gitolite/issues", "dependencies": [ { "name": "puppetlabs/stdlib", "version_requirement": ">= 3.2.0 < 7.0.0" }, { "name": "puppetlabs/concat", "version_requirement": ">= 2.0.0 < 7.0.0" }, { "name": "puppetlabs/cron_core", "version_requirement": ">= 0.0.0 < 2.0.0" } ], "operatingsystem_support": [ { "operatingsystem": "Debian", "operatingsystemrelease": [ "8", "9", "10" ] }, { "operatingsystem": "Ubuntu" } ], "requirements": [ { "name": "puppet", "version_requirement": ">=4.0.0 < 7.0.0" } ], "tags": [ "gitolite", "git" ], "pdk-version": "1.14.1", "template-url": "pdk-default#1.14.1", "template-ref": "1.14.1-0-g0b5b39b" } cirrax-gitolite-1.3.3/templates0040755000175000017500000000000013572015405013531 5ustar00cirrax-gitolite-1.3.3/templates/gitolite.rc.erb0100644000175000017500000000375513325601464016536 0ustar00# # PUPPET managed, do not edit ! # # configuration variables for gitolite # This file is in perl syntax. %RC = ( # default umask gives you perms of '0700'; see the rc file docs for # how/why you might change this UMASK => <%= @umask %>, # look for "git-config" in the documentation GIT_CONFIG_KEYS => '<%= @git_config_keys %>', # comment out if you don't need all the extra detail in the logfile <% if @log_extra -%> LOG_EXTRA => 1, <% end -%> LOG_DEST => '<%= @log_dest.join(',') %>', # roles. add more roles (like MANAGER, TESTER, ...) here. # WARNING: if you make changes to this hash, you MUST run 'gitolite # compile' afterward, and possibly also 'gitolite trigger POST_COMPILE' ROLES => { <% @roles.each do | role | -%> <%= role.ljust(20,' ') %> => 1, <% end -%> }, # the 'info' command prints this as additional info, if it is set <% if @site_info -%> SITE_INFO => '<%= @site_info %>', <% end -%> # the CpuTime feature uses these # display user, system, and elapsed times to user after each git operation # DISPLAY_CPU_TIME => 1, # display a warning if total CPU times (u, s, cu, cs) crosses this limit # CPU_TIME_WARN_LIMIT => 0.1, # the Mirroring feature needs this <% if @gitolite_hostname -%> HOSTNAME => "<%= @gitolite_hostname %>", <% end -%> <% if @local_code != '' -%> LOCAL_CODE => "<%= @local_code %>", <% end -%> <% @additional_gitoliterc.each do | key, val | -%> <%= key.ljust(30, ' ') %> => <%= val %>, <% end -%> # List of commands and features to enable ENABLE => [ <% @commands.each do | command | -%> '<%= command %>', <% end -%> ], # per perl rules, this should be the last line in such a file: ); <% @additional_gitoliterc_notrc.each do | key, val | -%> <%= key %> = <%= val %>; <% end -%> 1; cirrax-gitolite-1.3.3/templates/groups.erb0100644000175000017500000000044213162633200015610 0ustar00<% Array(@comments).each do |comment| -%> # <%= comment %> <% end -%> <% Array(@groups).each do |group| -%> <% if group =~ /^@/ -%> <%= group.ljust(15,' ') %> = <%= Array(@members).join(' ') %> <% else -%> @<%= group.ljust(14,' ') %> = <%= Array(@members).join(' ') %> <% end -%> <% end %> cirrax-gitolite-1.3.3/templates/repo.erb0100644000175000017500000000103413325434621015243 0ustar00<% Array(@comments).each do |comment| -%> # <%= comment %> <% end -%> repo <%= Array(@repos).join(' ') %> <% @rules.each do | rule, rval | -%> <%= rule.ljust(15,' ') %> = <%= Array(rval).join(' ') %> <% end -%> <% @options.each do | option, oval | -%> option <%= option.ljust(25,' ') %> = <%= oval %> <% end -%> <% @configs.each do | config, cval | -%> config <%= config.ljust(25,' ') %> = '<%= cval %>' <% end -%> <% @add_configs.each do | config, cval | -%> config <%= config.ljust(25,' ') %> = '<%= cval %>' <% end -%>