This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
while true; do /bin/echo -n .; sleep 30; done & | |
eval $* | |
STATUS=$? | |
kill $! | |
exit $STATUS |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Email for Let's Encrypt account | |
EMAIL="[email protected]" | |
# Install the CustomResourceDefinition resources separately | |
kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.6/deploy/manifests/00-crds.yaml | |
# Create the namespace for cert-manager | |
kubectl create namespace cert-manager |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FROM centos:8 | |
# Grab dependencies | |
RUN yum -y update && yum -y install python3-pip golang git | |
# Install AWS CLI | |
RUN pip3 install awscli | |
# Install ROSA CLI | |
RUN curl https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/rosa/latest/rosa-linux.tar.gz | tar -xzC /usr/local/bin rosa && /usr/local/bin/rosa completion > /etc/bash_completion.d/rosa |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: CI | |
# This workflow will purposely fail a check, then change that status to success. | |
# It will then approve and merge itself when a PR has been created. | |
# This is certainly not something you should usually do and I take no responsibility for how it's used. | |
# This is for informational purposes only. | |
on: | |
# Triggers the workflow on pull request events but only for the main branch | |
pull_request: |