Skip to content

Instantly share code, notes, and snippets.

View anthonygrees's full-sized avatar
🏠
Working from home

Anthony Rees anthonygrees

🏠
Working from home
View GitHub Profile
#!/usr/bin/env python3
import argparse
import configparser
import json
import subprocess
import sys
import os
import requests
stages: # List of stages for jobs, and their order of execution
- iac-scan
docker:image:
stage: iac-scan
image: docker:1.11
services:
- docker:dind
script:

Habitat On-Prem-Builder Depot authentication setup with Chef Automate

Step 1: create a new OAuth Application in Chef Automate

Login into your Automate server and create a file called oauth.toml

bldr_signin_url Is your builder FQDN. The URL should be http if you have SSL disabled which may be the case for an evaluation.

IMPORTANT: don't forget the / at the end of the URL you set for bldr_signin_url

@irvingpop
irvingpop / .gitignore
Last active January 30, 2023 22:31
Launch EC2 spot instances with tags, like a boss
MY_INSTANCEID
MY_SERVER
user-data.txt
.zshrc
.gitconfig
.ssh
.byobu
.oh-my-zsh
@jjasghar
jjasghar / vmware_chef.md
Created September 13, 2016 22:26 — forked from swalberg/vmware_chef.md
VMware and Chef Tools

VMware and Chef tools

Chef and VMware are a natural pairing and there are several tools available to enhance the integration.

Knife is a command-line tool that provides an interface between a local chef-repo and the Chef server and allows you to manipulate objects on the Chef server. Knife plugin allows your computer to talk to a 3rd party systems like vSphere or vRA. A plugin can create a VM in vSphere and then bootstrap it with Chef, for example, or it can expose your vRa catalog to your workstation so you don't need to use a GUI.

The following are the main interfaces with VMware and Chef our "knife" plugins.