palewire

How to push tagged Docker releases to Google Artifact Registry with a GitHub Action

Here's how I configured a GitHub Action so that a new version issued by GitHub's release interface will build a Dockerfile, tag it with the version number and upload it to Google Artifact Registry.

Before you attempt the steps below, you need the following:

• A GitHub repository that contains a working Dockerfile
• The Google Cloud SDK tool gcloud installed and authenticated

Create a Workload Identity Federation

erankitcs

{
    "variables": {
        "aws_region": "us-east-1",
        "base_ami": ""
    },
    "builders": [
        {
            "type": "amazon-ebs",
            "region": "{{user `aws_region`}}",
            "source_ami": "{{user `base_ami`}}",

mikesparr

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = ">= 3.37"
    }
    google-beta = {
      source  = "hashicorp/google-beta"
      version = ">= 3.37"
    }

wenerme

#!/bin/bash
set -e

fail(){
  echo "error: $*"
  echo "usage: ./k3s-new-cert <name> [subject=/O=admin]"
  exit 1
}

pedrohdz

// This Jenkins Groovy script extracts credentials in Jenkins and outputs them
// in a JSON format that can be digested by "Jenkins Configuration as Code".
// Just pass the output into a JSON to YAML converter.  You can run this
// through the Jenkins Script Console or similar.
//
// Thank you:
//  - https://github.com/tkrzeminski/jenkins-groovy-scripts/blob/master/show-all-credentials.groovy
//
// To conver to YAML `json2yaml | sed '/^[[:space:]]*$/d'`
//

bacongravy

require 'rubygems/package'

filenames_and_contents = {
  "filename" => "content",
}

File.open("archive.tar.gz", "wb") do |file|
  Zlib::GzipWriter.wrap(file) do |gzip|
    Gem::Package::TarWriter.new(gzip) do |tar|
      filenames_and_contents.each_pair do |filename, content|

gabrielrojasnyc

package main

import (
	"fmt"
	"log"
	"io"
	"os"
	"net/http"
	"time"
)

jcorioland

Create an Azure Container Service Kubernetes Cluster with Azure CLI

Login (interactive) to your Azure subscription using Azure CLI

az login

Create a resource group

miladoll

require 'fileutils'
require 'digest/md5'
require "itamae/resource/base"
require "itamae/logger"
module Itamae
    module Plugin
        module Resource
            class ExecuteOnce < Itamae::Resource::Base
                define_attribute :action, default: :execute_once
                define_attribute :cmd, type: String, default_name: true

section-io-gists

# Please note: There is an underlying default Varnish behavior that occurs after the VCL logic
# you see below. You can see the bultin code here
# https://github.com/varnishcache/varnish-cache/blob/5.1/bin/varnishd/builtin.vcl
#
# See the VCL chapters in the Users Guide at https://www.varnish-cache.org/docs/
# and http://varnish-cache.org/trac/wiki/VCLExamples for more examples.

# Marker to tell the VCL compiler that this VCL has been adapted to the
# new 4.0 format.
vcl 4.0;