By the way, I was very surprise to find out that the term "Gitcon" has not been reserved for "Git conference" so far.
What led me to this project was a set of requirements:
- As a start, the configuration means properties file
- As a start, only Git source repository needs to be supported
- As a start, it only needs to gets configuration for once when application starts. The configuration is used to populate Spring application context where beans are mostly singletons. Software owner needs to restart application to pick up configuration change.
- The library must be very friendly to Spring
- It gets file from Git repo authenticated via SSH key.
- The SSH private key must be configurable
- This is outside the scope of the library, but the SSH key comes from S3, which is authenticated by instance profile
- When SSH key is not specified, default one in user's home directory is applied. This is for development purpose.
- One Spring context may includes multiple properties coming from multiple repositories authenticated with different SSH keys.
- One properties file can include another under the same repository
The design is fairly straightforward. All it needs is to cope with the limitations from Jsch that JGit relies on.
S3FileFactoryBean is something that takes an IAM, a bucket and a key, downloads a file from S3 into local temporary directory, returns the file and deletes it when Spring context closes. Since the logic is generic to the purpose of Gitcon, it lives in a neutral package, kaufman-aws as artifact org.cyclopsgroup:kaufan-aws:0.0.2.
<bean id="gitSshKeyFile" class="org.cyclopsgroup.kaufman.aws.S3FileFactoryBean"> <constructor-arg value="my-s3-bucket" /> <constructor-arg value="my-app/git-ssh-private.key" /> </bean>
2. Clone, checkout Git repo with JGitThe easiest way to clone a Git repo is to use JGitLocalResourceRepository. With support from Eclipse JGit, this class defines Git repository URI, the access to Git repository and optionally the path to SSH private key. You may find out more details in Javadoc. An example:
<bean id="gitResourceRepo" class="org.cyclopsgroup.gitcon.spring.JGitLocalResourceRepository"> <constructor-arg value="email@example.com:me/my-runtime-config.git" /> <property name="sshIdentityFile" ref="gitSshKeyFile" /> </bean>
3. Create properties
The class GitconPropertiesFactoryBean simply creates Properties instance out of given ResourceRepository and a path to properties file. Since it creates Properties with ExtendedProperties, variable replacement and file inclusion is supported.
<bean id="appProperties" class="org.cyclopsgroup.gitcon.spring.GitconPropertiesBeanFactory"> <constructor-arg ref="gitResourceRepo" /> <constructor-arg value="myapp/myapp-prod.properties" /> </bean>
If you haven't tried, ExtendedProperties interprets properties file in a different way than Properties and exposes the content with a much more user friendly API. It is an ancient class from commons-collections, if a human is as old as this class, he would probably get a driver license by now.
4. Expand properties in Spring
This is done by a simple setup in Spring. It doesn't belong to Gitcon but I put it here so that the story is complete. The following config does the work.
<context:property-placeholder properties-ref="appProperties" />
To learn more
Like other CyclopsGroup projects, Gitcon Maven site is published to dist.cyclopsgroup.org/projects/gitcon. Very soon I will come up with a few wiki pages with official guides and examples.
Javadoc can be found here. Source code is in Github. The first version, org.cyclopsgroup:gitcon:0.0.1 has been published into Maven central repository.
If you have question, please feel free to contact me in Github, Facebook or Google+. Thank you for reading.