<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://16c7x.github.io/</id><title>16c7x</title><subtitle>Some where to for me to store useful documentation.</subtitle> <updated>2025-11-07T18:21:55+00:00</updated> <author> <name>Andrew Jones</name> <uri>https://16c7x.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://16c7x.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://16c7x.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2025 Andrew Jones </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>User email migration</title><link href="https://16c7x.github.io/posts/User-email-migration/" rel="alternate" type="text/html" title="User email migration" /><published>2025-11-06T11:12:00+00:00</published> <updated>2025-11-06T11:12:00+00:00</updated> <id>https://16c7x.github.io/posts/User-email-migration/</id> <content type="text/html" src="https://16c7x.github.io/posts/User-email-migration/" /> <author> <name>Andrew Jones</name> </author> <category term="Gitlab" /> <summary>User email migration The problem You may find yourself in a situation where all of your users email addresses need to change. This can happen if your organization is acquired by another or if your organization decides to go through a total rename and rebranding exercise. How do you change all of your Gitlab users email addresses, and how, as Gitlab uses users email addresses to link them to t...</summary> </entry> <entry><title>Secrets detection and removal</title><link href="https://16c7x.github.io/posts/Secrets_detection_and_removal/" rel="alternate" type="text/html" title="Secrets detection and removal" /><published>2025-10-20T12:12:00+01:00</published> <updated>2025-10-20T12:12:00+01:00</updated> <id>https://16c7x.github.io/posts/Secrets_detection_and_removal/</id> <content type="text/html" src="https://16c7x.github.io/posts/Secrets_detection_and_removal/" /> <author> <name>Andrew Jones</name> </author> <category term="Gitlab" /> <summary>Secrets detection and removal Secrets scanning policy Scan execution policies can be setup at the group level, it’s common for something like a secrets detection to be setup at the top level so it is applied globally. To enable, in the group where the policy is required go to Secure -&amp;gt; Policies and select New policy. Select Scan policy, most of the defaults can be left, just give it a name...</summary> </entry> <entry><title>Configuring LDAP in Puppet Enterprise</title><link href="https://16c7x.github.io/posts/configuring_ldap_in_puppet/" rel="alternate" type="text/html" title="Configuring LDAP in Puppet Enterprise" /><published>2024-07-16T12:00:00+01:00</published> <updated>2024-07-17T10:56:14+01:00</updated> <id>https://16c7x.github.io/posts/configuring_ldap_in_puppet/</id> <content type="text/html" src="https://16c7x.github.io/posts/configuring_ldap_in_puppet/" /> <author> <name>Andrew Jones</name> </author> <category term="Puppet Enterprise" /> <summary>Configuring LDAP in Puppet If you’re preparing to connect your Puppet Enterprise system to your production LDAP or you just want to learn a bit more about LDAP, it’s useful to test it out in a lab environment, this post is a basic walk through to get up and running with LDAP in Puppet Enterprise. LDAP Server The first thing we’re going to need is an LDAP server, building one from scratch wil...</summary> </entry> <entry><title>Puppet 8 rediness with Onceover</title><link href="https://16c7x.github.io/posts/Puppet_8_rediness_with_Onceover/" rel="alternate" type="text/html" title="Puppet 8 rediness with Onceover" /><published>2024-05-09T12:00:00+01:00</published> <updated>2024-06-04T16:43:37+01:00</updated> <id>https://16c7x.github.io/posts/Puppet_8_rediness_with_Onceover/</id> <content type="text/html" src="https://16c7x.github.io/posts/Puppet_8_rediness_with_Onceover/" /> <author> <name>Andrew Jones</name> </author> <category term="Puppet Enterprise" /> <summary>Puppet 8 readiness with Onceover Puppet 8 has been released, with it comes security enhancements, the dropping of deprecated features, and performance improvements, you can read more about Puppet 8 on this blog post. In this blog post, well look at how you can take your existing Puppet 7 code and use Onceover, a free testing tool, to test it against Puppet 8 to prepare for your migration. Pu...</summary> </entry> <entry><title>ssh-keygen</title><link href="https://16c7x.github.io/posts/keygen/" rel="alternate" type="text/html" title="ssh-keygen" /><published>2023-08-17T19:00:00+01:00</published> <updated>2023-08-18T10:40:58+01:00</updated> <id>https://16c7x.github.io/posts/keygen/</id> <content type="text/html" src="https://16c7x.github.io/posts/keygen/" /> <author> <name>Andrew Jones</name> </author> <category term="Scripting" /> <summary>ssh-keygen automation For a while I’ve wondered how to run ssh-keygen on a machine without user input, I’ve wanted to do this when deploying new machines in a CI/CD pipeline where I can’t answer ssh-keygen’s command line questions. It turns out to be so simple! yes y | ssh-keygen -t rsa -N '' -f /tmp/keys</summary> </entry> </feed>
