coordt

{
  "title": "Values",
  "description": "Basic contents of a Values file.",
  "type": "object",
  "properties": {
    "defaultComponent": {
      "title": "Defaultcomponent",
      "description": "The default configurations of a component, if not overridden.",
      "allOf": [
        {

coordt

#!/usr/bin/env bash
# Generate the changelog, make a release if necessary and return the version number

# Pass in the path to the source repo so the appropriate __init__.py file is changed
SOURCE_DIR=$1

# The first 20 characters of the branch name for development releases
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD | cut -c 1-20)

# Generate the changelog and get the release hint

coordt

Releasing Software

What is a software release?

A release is the immutable packaging of a software product. Software releases are an essential component of modern software development and the software development life cycle for two main reasons:

• They are intentional. Someone decided what changes are required to give value and when the changes are ready for others to use.
• They include context. Information about the difference between the code at two points is conveyed. Whether it is simply by the version indicating the scope or including additional artifacts such as a changelog, the user has more information than "something changed."

The developer plays a key role in a software release because a thoughtful decision is required.

coordt

[
  {
    "model": "saml2auth.identityprovider",
    "pk": 1,
    "fields": {
      "name": "Peerfit",
      "slug": "peerfit",
      "metadata_url": "",
      "permission_attrs": "{\"is_active\":true,\"is_staff\":true,\"is_superuser\":false}",
      "sp_config": "{\"name_id_format\":\"urn:oasis:names:tc:SAML:2.0:nameid-format:persistent\",\"authn_requests_signed\":true,\"want_response_signed\":true,\"force_authn\":true,\"allow_unsolicited\":true,\"want_assertions_signed\":true,\"logout_requests_signed\":true,\"required_attributes\":[],\"optional_attributes\":[]}",

coordt

Keybase proof

I hereby claim:

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

To claim this, I am signing this object:

coordt

AWSTemplateFormatVersion: 2010-09-09
Description: Test Server Infrastructure
Parameters:
  ParentVPCStack:
    Description: 'Stack name of parent VPC stack based on vpc/vpc-*azs.yaml template.'
    Type: String
    Default: 'TestVPC'
  ParentSSHBastionStack:
    Description: 'Optional but recommended stack name of parent SSH bastion host/instance stack based on vpc/vpc-ssh-bastion.yaml template.'
    Type: String

coordt

---
AWSTemplateFormatVersion: 2010-09-09
Description: Test Server Infrastructure
Parameters:
  ParentVPCStack:
    Description: Stack name of parent VPC stack based on vpc/vpc-*azs.yaml template.
    Type: String
    Default: 'TestVPC'
  ParentSSHBastionStack:
    Description: 'Optional but recommended stack name of parent SSH bastion host/instance stack based on vpc/vpc-ssh-bastion.yaml template.'

coordt

# -*- coding: utf-8 -*-
from __future__ import unicode_literals
import os

from fabric.api import cd, run, sudo, prefix, task, env, quiet, warn_only
from fabric.contrib.files import exists, sed
from fabric.tasks import Task

# The information to connecting to the server: `testserver` is contained
# in the local user's `~/.ssh/config` file

coordt

"""
Tasks for managing a test server
"""
import os
from fabric.api import cd, env, prefix, run, sudo, task
from fabric.contrib.files import exists, sed
from fabric.context_managers import hide
from fabric.colors import green, red

coordt

#!/usr/bin/env python
## WARNING: This file is generated
#!/usr/bin/env python
"""Create a "virtual" Python installation
"""

# If you change the version here, change it in setup.py 
# and docs/conf.py as well.
virtualenv_version = "1.6.3"