pupistry 0.0.13 → 1.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +3 -15
- data/resources/aws/README_AWS.md +4 -0
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: d510aff9adf9c6b3be5c31627368e8f121cd688b
|
4
|
+
data.tar.gz: 1ea65ab0a96149ce31b622cadbfda987ea1583d1
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 15f88302ae54dd109db24ec08a8ae0852edb75070f0ef7f80ade1f15c1e5fd53f9b631624c9d04e7200cd4e372a6aa4e8d1b7b139362a6a1d41425d5a55aa205
|
7
|
+
data.tar.gz: c18e071d7a52a28ea87d656fc5942b6ae27a3c2adefdd9bc41d74ca4ce980f64152eab386505caef9e4e9f1e38fd3889c55a7706f5050eddf7169d43da2fe46c
|
data/README.md
CHANGED
@@ -1,15 +1,3 @@
|
|
1
|
-
# WORK IN PROGRESS
|
2
|
-
|
3
|
-
This project is currently in progress and not all of this documentation reflects
|
4
|
-
where it is really at. Use this at your own peril/madness. In theory, everything
|
5
|
-
currently works, but there will be bugs and areas of the documentation that may
|
6
|
-
not make sense.
|
7
|
-
|
8
|
-
I've marked anything I can that is in progress with TODO and workarounds/notes
|
9
|
-
where I can. It's all under development ATM so it's changing really fast, but
|
10
|
-
I'll happily take pull requests at even this early stage.
|
11
|
-
|
12
|
-
|
13
1
|
# pupistry
|
14
2
|
|
15
3
|
Pupistry (puppet + artistry) is a solution for implementing reliable and secure
|
@@ -215,7 +203,7 @@ Alternatively if you like living on the edge, download this repository and run:
|
|
215
203
|
pupistry setup
|
216
204
|
|
217
205
|
Pupistry will write an example config file into `~/.pupistry/settings.yaml` for
|
218
|
-
you.
|
206
|
+
you, you will need to edit it with your preferred editor.
|
219
207
|
|
220
208
|
|
221
209
|
## 2. S3 Bucket
|
@@ -266,7 +254,7 @@ error) with:
|
|
266
254
|
|
267
255
|
Once status is CREATE_COMPLETE, you can get all the outputs from the stack with:
|
268
256
|
|
269
|
-
aws cloudformation describe-stacks --query "Stacks[*].Outputs[*]" --stack-name pupistry-resources
|
257
|
+
aws cloudformation describe-stacks --query "Stacks[*].Outputs[*]" --stack-name pupistry-resources-changeme
|
270
258
|
|
271
259
|
You now need to edit `~/.pupistry/settings.yaml` and enter in the equalivent
|
272
260
|
OutputValue for the following labels:
|
@@ -400,7 +388,7 @@ third parties other than your VM provider and AWS S3.
|
|
400
388
|
If you're looking for a more complete introduction to doing masterless Puppet
|
401
389
|
and want to use Pupistry, check out a tutorial by the author:
|
402
390
|
|
403
|
-
|
391
|
+
https://www.jethrocarr.com/2015/05/10/setting-up-and-using-pupistry
|
404
392
|
|
405
393
|
By following this tutorial you can go from nothing, to having a complete up
|
406
394
|
and running masterless Puppet environment using Pupistry. It covers the very
|
data/resources/aws/README_AWS.md
CHANGED
@@ -59,6 +59,10 @@ artifacts) then it will fail to delete. Make sure you delete all items from
|
|
59
59
|
the S3 bucket first, then delete the stack. This is generally considered a
|
60
60
|
useful safety feature. ;-)
|
61
61
|
|
62
|
+
You can delete all items with:
|
63
|
+
|
64
|
+
aws s3 rm --recursive s3://pupistry-resources-changeme
|
65
|
+
|
62
66
|
|
63
67
|
## Developer Notes
|
64
68
|
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: pupistry
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0
|
4
|
+
version: 1.0.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Jethro Carr
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2015-05-
|
11
|
+
date: 2015-05-10 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: aws-sdk-v1
|