tl;dr version: " $ { e l e m e n t ( d a t a . g i t h u b _ t e a m . p u l l . * . i d , c o u n t . i n d e x ) } " While writing a little terraform module to manage github repositories, team permissions and branch protection rules, I ran into an issue where github_team_repository resources need the team ID, but github_branch_protection resources need the team slug. ...
Background A few weeks ago I decided to replace my ageing and bloated Drupal 7 blog. I decided on the following criteria that the solution had to meet: The project git repo must be private. Hosting infrastructure had to be under my control and completely codified. The solution should require very little supporting infrastructure such as databases. Deployment of changes to the site or infrastructure must be automated. These requirements immediately ruled out a few options including GitHub Pages and SaaS blogging platforms like wordpress.org. ...
During a recent project, I ran into an issue where the new stack (defined using Terraform) needed to connect to a legacy server via private network interfaces. The Terraform stack was encapsulated within its own VPC, and the legacy server was in the default VPC. Both VPCs were in the same region. AWS has a feature called “VPC peering” which establishes a connection between two VPCs - exactly what was required for this use case. AWS has some documentation available, but I wasn’t able to find any clear examples on how to achieve this with Terraform (inspiring this post). ...