jevonearth

Keybase proof

I hereby claim:

• I am jevonearth on github.
• I am jevonearth (https://keybase.io/jevonearth) on keybase.
• I have a public key ASC_MjtGWsg9K4cNiJJuOKoNX3rduGWuL3w3VXPbtpHhVAo

To claim this, I am signing this object:

jevonearth

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kibana-ingress
  annotations:
    kubernetes.io/ingress.class: traefik
    traefik.backend.loadbalancer.sticky: "true"
    ingress.kubernetes.io/rewrite-target: "/"
spec:
  tls:

jevonearth

---
- name: check if node_exporter binary exists
  stat: path=/usr/local/bin/node_exporter
  register: node_exporter_stat

- name: check version
  shell: /usr/local/bin/node_exporter -version|head -1|awk '{print $3}'
  check_mode: no
  ignore_errors: yes
  changed_when: false

jevonearth

2016/11/03 13:40:51 [INFO] Packer version: 0.11.1.dev (ed3c6f29effb32bec300d3e9b72472cac5d0fd06)
2016/11/03 13:40:51 Packer Target OS/Arch: linux amd64
2016/11/03 13:40:51 Built with Go Version: go1.7.3
2016/11/03 13:40:51 Detected home directory from env var: /home/jev
2016/11/03 13:40:51 Using internal plugin for null
2016/11/03 13:40:51 Using internal plugin for qemu
2016/11/03 13:40:51 Using internal plugin for virtualbox-iso
2016/11/03 13:40:51 Using internal plugin for docker
2016/11/03 13:40:51 Using internal plugin for file
2016/11/03 13:40:51 Using internal plugin for parallels-pvm

jevonearth

{
  "builders": [
    {
      "image_name": "foo_base_gcp_11_0_{{timestamp}}",
      "account_file": "../gcp_account.json",
      "name": "foo-base-gcp-freebsd11",
      "zone": "us-west1-a",
      "disk_size": "30",
      "source_image": "freebsd-11-0-release-p1-amd64",
      "source_image_project_id": "freebsd-org-cloud-dev",

jevonearth

 ⚙ jev@tower  ~/projects/foo/infrastructure/packer   master ●  PACKER_LOG=1 packer-io build simple.json |tee log
2016/11/01 15:04:07 [INFO] Packer version: 0.11.0
2016/11/01 15:04:07 Packer Target OS/Arch: linux amd64
2016/11/01 15:04:07 Built with Go Version: go1.7.3
2016/11/01 15:04:07 Detected home directory from env var: /home/jev
2016/11/01 15:04:07 Using internal plugin for vmware-iso
2016/11/01 15:04:07 Using internal plugin for vmware-vmx
2016/11/01 15:04:07 Using internal plugin for openstack
2016/11/01 15:04:07 Using internal plugin for virtualbox-iso
2016/11/01 15:04:07 Using internal plugin for digitalocean

jevonearth

import requests
from requests.auth import HTTPBasicAuth
import re
from StringIO import StringIO

JIRA_URL = 'https://your-jira-url.tld/'
JIRA_ACCOUNT = ('jira-username', 'jira-password')
# the JIRA project ID (short)
JIRA_PROJECT = 'PRO'
GITLAB_URL = 'http://your-gitlab-url.tld/'

jevonearth

# Maintainer: CYB3R <dima@golovin.in>
# Contributor: Sarkasper <kasper.menten@gmx.com>
# Contributor: Scias <shining.scias@gmail.com>
# Contributor: darzki <darzki@o2.pl>
# Contributor: N30N <archlinux@alunamation.com>
 
pkgname=("lwks")
provides=("lightworks")
pkgver=11.5.B
pkgrel=1

jevonearth

<?xml version="1.0" encoding="UTF-8"?>
<Response>
<Dial>
    <Sip>
        sip:123@67.228.3.77
    </Sip>
</Dial>
</Response>

jevonearth

/*
The CRUD methods in ForceApi all take java objects, and  de-serializes them to json internally. 
I do not want to annotate my domain objects specifically for sobjects, instead I would like to manage my own serialization.

Perhaps we could add an additional method per CRUD method which takes a json string instead of a Object, allowing the client more control of how it manages its domain model.
*/
	
    public String createSObject(String type, Object sObject) {
		return createSObject(type, jsonMapper.writeValueAsBytes(sObject));
	}