Author: Sean Gillies Version: 1.0
This document describes a GeoJSON-like protocol for geo-spatial (GIS) vector data.
| license: gpl-3.0 |
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
When you modify a file in your repository, the change is initially unstaged. In order to commit it, you must stage it—that is, add it to the index—using git add. When you make a commit, the changes that are committed are those that have been added to the index.
git reset changes, at minimum, where your current branch is pointing. The difference between --mixed and --soft is whether or not your index is also modified. So, if we're on branch master with this series of commits:
- A - B - C (master)
HEADpoints to C and the index matches C.
| def rasterize_geom(geom, src_offset, new_gt, all_touched): | |
| from rasterio import features | |
| geoms = [(geom, 1)] | |
| rv_array = features.rasterize( | |
| geoms, | |
| out_shape=(src_offset[3], src_offset[2]), | |
| transform=new_gt, | |
| fill=0, | |
| all_touched=all_touched) | |
| return rv_array |
This gist will contain all the exercises from the book
ansible-playbook --connection=local 127.0.0.1 playbook.yml127.0.0.1 ansible_connection=local