int128

associatedPullRequestsInCommitHistoryOfSubTree

This query returns a list of pull request in the commit history of a sub tree in a repository.

Problem to solve

Let us think about a monorepo, for example,

int128

This page has been moved to https://github.com/int128/hello-envoy

---

Envoy TCP Proxy

This is an example of Envoy TCP Proxy from localhost:10000 to www.google.com:80. See also https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/listeners/tcp_proxy.

To run a proxy:

int128

query { 
  repository(owner: "int128", name: "kubelogin") {
    defaultBranchRef {
      target {
        ... on Commit {
          file(path: "/.github/workflows") {
            type
            object {
              ... on Tree {
                entries {

int128

FROM alpine:3.11
ARG VERSION
#TODO: add steps

int128

mkfifo /tmp/pipe;

(tee -a /var/log/kube-apiserver.log < /tmp/pipe & ) ;

exec /usr/local/bin/kube-apiserver 
--allow-privileged=true 
--anonymous-auth=false 
--apiserver-count=1 
--authorization-mode=RBAC 
--basic-auth-file=/srv/kubernetes/basic_auth.csv 

int128

/**
 * Create a ZIP/JAR file with given contents.
 *
 * @param destination destination file
 * @param contents map of filename and content
 */
void createZIP(File destination, Map<String, String> contents) {
    destination.withOutputStream {
        new ZipOutputStream(it).withStream { zip ->
            contents.each { filename, content ->

int128

package main

import (
	"crypto/tls"
	"crypto/x509"
	"io/ioutil"
	"log"
	"net/http"
)

int128

AWS CodeBuild to GitBucket access

GET /USER/REPO/info/refs?service=git-upload-pack HTTP/1.1" 301
GET /git/USER/REPO/info/refs?service=git-upload-pack HTTP/1.1" 200
POST /git/USER/REPO/git-upload-pack HTTP/1.1" 200
GET /USER/REPO/info/refs?service=git-upload-pack HTTP/1.1" 301
GET /git/USER/REPO/info/refs?service=git-upload-pack HTTP/1.1" 200
POST /api/v3/repos/USER/REPO/statuses/1c99b9292c2bec3f31fa67456797b10ec8405ef5 HTTP/1.1" 401
POST /api/v3/repos/USER/REPO/statuses/1c99b9292c2bec3f31fa67456797b10ec8405ef5 HTTP/1.1" 401

int128

GitLab SAML SSO with Keycloak

Keycloak

1. Open your Keycloak realm.
2. Import keycloak-gitlab.json.
3. Fix URLs of the client.

GitLab

int128

sudo systemctl stop docker-healthcheck.timer
sudo systemctl stop docker
sudo systemctl stop kubelet
sudo systemctl stop protokube

sudo systemctl --all shows: