<feed xmlns='http://www.w3.org/2005/Atom'>
<title>csa/devops/ansible-patches/openshift.git/roles/openshift_project_request_template, branch ands</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.ru.suren.me/cgit/csa/devops/ansible-patches/openshift.git/'/>
<entry>
<title>Remove openshift.common.{is_atomic|is_containerized}</title>
<updated>2017-12-20T15:13:51+00:00</updated>
<author>
<name>Michael Gugino</name>
<email>mgugino@redhat.com</email>
</author>
<published>2017-12-18T21:13:36+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.ru.suren.me/cgit/csa/devops/ansible-patches/openshift.git/commit/?id=e6c159afb4ba39a7266c750d43d6a5e911cc8f21'/>
<id>e6c159afb4ba39a7266c750d43d6a5e911cc8f21</id>
<content type='text'>
We set these variables using facts in init, no need
to duplicate the logic all around the codebase.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We set these variables using facts in init, no need
to duplicate the logic all around the codebase.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add role to configure project request template</title>
<updated>2017-10-23T12:59:53+00:00</updated>
<author>
<name>Michael Hanselmann</name>
<email>hansmi@vshn.ch</email>
</author>
<published>2017-09-22T13:36:51+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.ru.suren.me/cgit/csa/devops/ansible-patches/openshift.git/commit/?id=6039b8928ba8b172d95f10c9d0ae7880f393f2f7'/>
<id>6039b8928ba8b172d95f10c9d0ae7880f393f2f7</id>
<content type='text'>
The OpenShift master role already supports changing the master
configuration to refer to a project template, but there's no way to
manage that template directly. This role adds the necessary code to
generate a default template and to apply customizations using the
"yedit" module.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The OpenShift master role already supports changing the master
configuration to refer to a project template, but there's no way to
manage that template directly. This role adds the necessary code to
generate a default template and to apply customizations using the
"yedit" module.
</pre>
</div>
</content>
</entry>
</feed>
