fpletz

#!/usr/bin/env python3

import aioesphomeapi
import asyncio

async def main():
    loop = asyncio.get_running_loop()
    cli = aioesphomeapi.APIClient(loop, "foobarhostname", 6053, "foobarpassword")

    await cli.connect(login=True)

BRMatt

#!/usr/bin/env ruby

resources = $stdin.readlines.map(&:split).flatten.map do |resource|
  {
    module: resource.scan(%r{module\.([a-z0-9\-_]+)}).to_a.join("."),
    identifier: resource.match(%r{(?:module\.[a-z0-9\-_]+\.)*(.*)$}).captures.first,
  }
end

resources.each do |resource|

lovemyliwu

class CustomTask(Task):
    def on_failure(self, exc, task_id, args, kwargs, einfo):
        info = '[{0}] failed: {1}'.format(task_id, exc)
        logger.exception(info, exc_info=exc)
        super(CustomTask, self).on_failure(exc, task_id, args, kwargs, einfo)

    def on_success(self, retval, task_id, args, kwargs):
        global app
        if app.is_warm_shutdown:
            app.consumer.connection._default_channel.do_restore = False

cheeseplus

One of the earliest lessons in a users' journey with using Chef is how to bootstrap a node with knife. Most of the tutorials will very reasonably illustrate some form of knife bootstrap but the immediate follow on question is often, how do I do this in production? The answer to that question is less directly clear because different infrastructure needs will lend themselves to different approaches. With the following I want to break down "bootstrapping" and illustrate a few approaches. This is not meant to be a comprehensive review of evertyhing possible but a deconstruction of the primitives in play.

a brief detour regarding validation

Since Chef 12.2.0, the default bootstrapping method is "validatorless" - which as the name implies, exists in opposition to the fomer "validator" based approach. The older approach makes use of the unique org "validator" key that is created as part of an organisation on chef-server, you may have seen it referenced as "validation.pem" or "org-validator", which allows an

Faheetah

node {
    echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1'
    echo 'No quotes, pipeline command in single quotes'
    sh 'echo $BUILD_NUMBER' // 1
    echo 'Double quotes are silently dropped'
    sh 'echo "$BUILD_NUMBER"' // 1
    echo 'Even escaped with a single backslash they are dropped'
    sh 'echo \"$BUILD_NUMBER\"' // 1
    echo 'Using two backslashes, the quotes are preserved'
    sh 'echo \\"$BUILD_NUMBER\\"' // "1"

rlouapre

FROM centos:centos6
MAINTAINER Richard Louapre <richard.louapre@marklogic.com>
 
#update yum repository and install openssh server
RUN yum update -y
RUN yum install -y openssh-server
 
#generate ssh key
RUN ssh-keygen -q -N "" -t dsa -f /etc/ssh/ssh_host_dsa_key
RUN ssh-keygen -q -N "" -t rsa -f /etc/ssh/ssh_host_rsa_key

karmi

#!/usr/bin/env bash
#
# ===================================
# Experiments with the HBase REST API
# ===================================
#
# <http://hbase.apache.org/docs/r0.20.4/api/org/apache/hadoop/hbase/rest/package-summary.html>
#
# Usage:
#