Please refer to this blogpost to get an overview.
Replace *-INSTANCE
with one of the public instances listed in the scrapers section. Replace CAPITALIZED
words with their corresponding identifiers on the website.
apiVersion: v1 | |
kind: ConfigMap | |
metadata: | |
name: maintenance-page | |
data: | |
maintenance.html: |- | |
<!--HTML GOES HERE--> | |
<!doctype html> | |
<title>Site Maintenance</title> | |
<link rel="stylesheet" href="maintenance.css"> |
# Source: https://gist.github.com/0d73463668d1f75ac0e94c7cd7d03fed | |
############################################### | |
# GitHub CLI # | |
# How to manage repositories more efficiently # | |
# https://youtu.be/BII6ZY2Rnlc # | |
############################################### | |
# Referenced videos: | |
# - Ketch - How to Simplify Kubernetes Deployments: https://youtu.be/sMOIiTfGnj0 |
AWSTemplateFormatVersion: "2010-09-09" | |
Description: Template test-MyBucket1 and 2 by manuel.cruanes 2022-09-29 | |
Resources: | |
MyBucket2: | |
Type: AWS::S3::Bucket | |
Properties: | |
BucketName: photobox-dev-test-my-bucket2 | |
Tags: | |
- | |
Key: "Owner" |
Please refer to this blogpost to get an overview.
Replace *-INSTANCE
with one of the public instances listed in the scrapers section. Replace CAPITALIZED
words with their corresponding identifiers on the website.
<iframe src="https://www.google.com/maps/embed?pb=!1m14!1m8!1m3!1d56790.47490202523!2d78.042155!3d27.175014999999924!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x39747121d702ff6d%3A0xdd2ae4803f767dde!2sTaj+Mahal!5e0!3m2!1sen!2s!4v1398864446719" width="800" height="600" frameborder="0" style="border:0"></iframe> |
# Source: https://gist.github.com/4e2fd2696ef7d5ce6a915a2eb2408e17 | |
################################################################### | |
# How To Manage Production-Grade Kubernetes Clusters With Rancher # | |
# https://youtu.be/JFALdhtBxR8 # | |
################################################################### | |
# Additional Info: | |
# - Rancher: https://rancher.com/products/rancher | |
# - Rancher Fleet: GitOps Across A Large Number Of Kubernetes Clusters: https://youtu.be/rIH_2CUXmwM |
# Source: https://gist.github.com/vfarcic/70a14c8f15c7ffa533ea7feb75341545 | |
###################### | |
# Create The Cluster # | |
###################### | |
# Make sure that you're using eksctl v0.1.5+. | |
# Follow the instructions from https://github.com/weaveworks/eksctl to intall eksctl. |
# --------------------------------------------------------------------------------------------------------------------- | |
# ENVIRONMENT VARIABLES | |
# Define these secrets as environment variables | |
# --------------------------------------------------------------------------------------------------------------------- | |
# AWS_ACCESS_KEY_ID | |
# AWS_SECRET_ACCESS_KEY | |
# --------------------------------------------------------------------------------------------------------------------- | |
# REQUIRED PARAMETERS |
-- Ansible testing using Assert | |
When we run Ansible to manage server configurations, we assume (if there is no red errors) that it worked. But if you are developing ansible modules for your systems, and want to take the DevOps approach and work on CICD pipelines, you need to have some tests in there to prove that what you asked ansible to do has actually worked. | |
One of the best ways to do this within ansible, is to use the Assert module. It asserts that a given expression is true. When you combine this with the output of a command that’s registered to a variable, there is almost no limit to what you can test. | |
I’m going to use the TDD (Test driven development) method where we create the tests before we start writing any ansible code to manage our systems. I expect the tests to fail. Then we’ll write ansible to pass the tests. That’s it. | |
This demo will cover the following: | |
• Create some tests using the command and assert modules. |