mailman-2097

----------
## Please do not copy paste commands blindly. Make your own runsheet.

----------
## Auto

$ ping archlinux.org
$ pacman -Sy archlinux-keyring
$ archinstall

mailman-2097

AD-XX: <TOPIC - short, concise summary>

• Date: <DATE - when the decision was made>
• Driver: <DRIVER - list a single person driving consenus and decision making>
• Stakeholders: <STAKEHOLDERS - list all relevant stakeholders affected by this decision>
• Status: [PROPOSED | DECIDED | SUPERSEDED]
• Categories: <CATEGORIES - use a simple grouping to help organize the set of decisions (e.g. backend, payment, user management, ...)>
• Outcome: <OUTCOME - once decided, provide a short summary of the decision outcome here>

Context

mailman-2097

Be very clear on who your stakeholders are. If unsure, ask

Proactively bring impacted parties into the fold

Look for win-win-wins (Customers, Your team, Yourself personally)

Overcommunicate. Set Agenda’s & Send out Minutes for all Customer meetings

Be aware of political implications of everything you do

mailman-2097

It looks like proxy is aborting connection. After some debugging using openssl, tcpdump and curl, I observed that the rhui3 server is rejecting the SSL connection if we connect via https_proxy (NAT) without a valid certificate. 

I could see that this instance is connecting to the outside world via squid proxy's network interface (eni-04555c95115a75e50.  Looking at the squid configuration, I assume that you might have setup transparent squid proxy as per the following blog post. So you dont have to explicitly define proxy variables in redhat instance.

https://aws.amazon.com/blogs/security/how-to-add-dns-filtering-to-your-nat-instance-with-squid/ 

I would suggest you to update your proxy configuration to bypass ssl certificate validation as given below and check if yum update works.

1. Append the following line to your squid configuration file

mailman-2097

# -*- mode: ruby -*-
# vi: set ft=ruby :

IP_SRVR = "192.168.76.76"


VAGRANTFILE_API_VERSION = "2"
BOX_IMAGE = "geerlingguy/ubuntu1804"
SRVR_COND = true

mailman-2097

# -----------------------
# Inline Policy
# -----------------------

resource "aws_iam_role" "iam_ser" {
  name_prefix          = "svc-${var.workload_name}-bake"
  permissions_boundary = "arn:aws:iam::${data.aws_caller_identity.current.account_id}:policy/WorkloadPermissionsBoundary"
  assume_role_policy = jsonencode({
    "Version" : "2012-10-17",
    "Statement" : [

mailman-2097

locals {
  common_files   = [formatlist("%s/%s", "src/common", fileset("${path.module}/src/common", "*.*"))]
  helpers_files  = [formatlist("%s/%s", "src/helpers", fileset("${path.module}/src/helpers", "*.*"))]
  starter_files  = [formatlist("%s/%s", "src/starter", fileset("${path.module}/src/starter", "*.*"))]
  combined_files = flatten(concat(local.common_files, local.helpers_files, local.starter_files))
}

data "template_file" "t_file" {
  count = length(local.combined_files)
  template = "${file(element(local.combined_files, count.index))}"

mailman-2097

data "aws_iam_policy_document" "kms_policy" {
  statement {
    sid       = "Enable Root user permissions"
    effect    = "Allow"
    actions   = ["kms:*"]
    resources = ["*"]
    principals {
      type = "AWS"
      identifiers = [
        "arn:aws:iam::${local.account_id}:root",

mailman-2097

#region Ensure the WinRm service is running
Set-Service -Name "WinRM" -StartupType Automatic
Start-Service -Name "WinRM"
#endregion

#region Enable PS remoting
if (-not (Get-PSSessionConfiguration) -or (-not (Get-ChildItem WSMan:\localhost\Listener))) {
    Enable-PSRemoting -SkipNetworkProfileCheck -Force
}
#endregion

mailman-2097

"""
This is a work in progress. But a good place to start for manipulating YAML with python.
Ex: for the below input yaml it will replace the variables in resource string with values provided in context.
---
action:
    resource: mysql://${db_user}:${db_pass}@${db_host}:3306/wordpress
    context: {db_pass: ch33s3, db_user: lchan, db_host: localhost }
    
"""
#!/usr/bin/env python