oldwombat

# Adjust the following variables as necessary
REMOTE=origin
BRANCH=$(git rev-parse --abbrev-ref HEAD)
BATCH_SIZE=250

# check if the branch exists on the remote
if git show-ref --quiet --verify refs/remotes/$REMOTE/$BRANCH; then
    # if so, only push the commits that are not on the remote already
    range=$REMOTE/$BRANCH..HEAD
else

oldwombat

• Simple and flexible horizontal and vertical scaling
• Consistent tooling for all deployments, customisations, addons in Kube YAML
• Allows for the complexity and customisation of old VM based networks, with the flexibility and scalability of containers
• Containerisation + microservices architecture - isolating and running each microservice as a versionable container and managing it's resources, scaling and availability
  • Optimised for autoscaling - cost optimisation via rapid and automated scaling when needed
  • Flexible multi-container pods to enforce compliance or security requirements eg logging, service mesh, traffic scanning etc
  • Network Policy as code - apply ingress and egress network rules between Pods and Nodes
  • Everything as Code > auditable, scannable, versionable
• Everything deployed, configured and maintained as code
• Supports rapid deployment of code (read: features & hotfixes), limiting blast radius

oldwombat

#
# README
#

# Open the Azure Cloud Shell
# Run Connect-AzureAD
# Authenticate if needed
# Confirm that all your groups are listed in the $AllGroups var
# Upload add-to-groups.ps1 if needed
# Run ./add-user-to-ad-groups.ps1 "[email protected]"