cloudformation-tool 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/LICENSE +339 -0
- data/README.md +204 -0
- data/bin/cftool +9 -0
- data/lib/cloud_formation_tool.rb +94 -0
- data/lib/cloud_formation_tool/cli.rb +5 -0
- data/lib/cloud_formation_tool/cli/compile.rb +19 -0
- data/lib/cloud_formation_tool/cli/create.rb +50 -0
- data/lib/cloud_formation_tool/cli/delete.rb +18 -0
- data/lib/cloud_formation_tool/cli/list_stacks.rb +15 -0
- data/lib/cloud_formation_tool/cli/main.rb +31 -0
- data/lib/cloud_formation_tool/cli/monitor.rb +28 -0
- data/lib/cloud_formation_tool/cli/parameters.rb +20 -0
- data/lib/cloud_formation_tool/cli/servers.rb +30 -0
- data/lib/cloud_formation_tool/cli/status.rb +18 -0
- data/lib/cloud_formation_tool/cloud_formation.rb +153 -0
- data/lib/cloud_formation_tool/cloud_formation/lambda_code.rb +41 -0
- data/lib/cloud_formation_tool/cloud_formation/stack.rb +152 -0
- data/lib/cloud_formation_tool/cloud_init.rb +86 -0
- data/lib/cloud_formation_tool/errors.rb +11 -0
- data/lib/cloud_formation_tool/storable.rb +41 -0
- data/lib/cloud_formation_tool/version.rb +3 -0
- metadata +109 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 76594dd22665ad87aa9cd9e2e6541b85d6a21b7a
|
4
|
+
data.tar.gz: 6089b920121308b4a738290e9c87f0c412676799
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: e205fb54c469ae9cff48099a609f8392954a554067b5d1f62b9eb3889c3d9032146fb9d00e554e860f6048d398b35362bd94190a84df105a12c2b219bcb14754
|
7
|
+
data.tar.gz: e63f990eb5d34f4a60678acd36b3ec1c774781119aa8f3481cbf362b43a0dea32ca17931937932728504fc79af9c01e4db553f7fbc32a3326b49177cd2477601
|
data/LICENSE
ADDED
@@ -0,0 +1,339 @@
|
|
1
|
+
GNU GENERAL PUBLIC LICENSE
|
2
|
+
Version 2, June 1991
|
3
|
+
|
4
|
+
Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
|
5
|
+
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
|
6
|
+
Everyone is permitted to copy and distribute verbatim copies
|
7
|
+
of this license document, but changing it is not allowed.
|
8
|
+
|
9
|
+
Preamble
|
10
|
+
|
11
|
+
The licenses for most software are designed to take away your
|
12
|
+
freedom to share and change it. By contrast, the GNU General Public
|
13
|
+
License is intended to guarantee your freedom to share and change free
|
14
|
+
software--to make sure the software is free for all its users. This
|
15
|
+
General Public License applies to most of the Free Software
|
16
|
+
Foundation's software and to any other program whose authors commit to
|
17
|
+
using it. (Some other Free Software Foundation software is covered by
|
18
|
+
the GNU Lesser General Public License instead.) You can apply it to
|
19
|
+
your programs, too.
|
20
|
+
|
21
|
+
When we speak of free software, we are referring to freedom, not
|
22
|
+
price. Our General Public Licenses are designed to make sure that you
|
23
|
+
have the freedom to distribute copies of free software (and charge for
|
24
|
+
this service if you wish), that you receive source code or can get it
|
25
|
+
if you want it, that you can change the software or use pieces of it
|
26
|
+
in new free programs; and that you know you can do these things.
|
27
|
+
|
28
|
+
To protect your rights, we need to make restrictions that forbid
|
29
|
+
anyone to deny you these rights or to ask you to surrender the rights.
|
30
|
+
These restrictions translate to certain responsibilities for you if you
|
31
|
+
distribute copies of the software, or if you modify it.
|
32
|
+
|
33
|
+
For example, if you distribute copies of such a program, whether
|
34
|
+
gratis or for a fee, you must give the recipients all the rights that
|
35
|
+
you have. You must make sure that they, too, receive or can get the
|
36
|
+
source code. And you must show them these terms so they know their
|
37
|
+
rights.
|
38
|
+
|
39
|
+
We protect your rights with two steps: (1) copyright the software, and
|
40
|
+
(2) offer you this license which gives you legal permission to copy,
|
41
|
+
distribute and/or modify the software.
|
42
|
+
|
43
|
+
Also, for each author's protection and ours, we want to make certain
|
44
|
+
that everyone understands that there is no warranty for this free
|
45
|
+
software. If the software is modified by someone else and passed on, we
|
46
|
+
want its recipients to know that what they have is not the original, so
|
47
|
+
that any problems introduced by others will not reflect on the original
|
48
|
+
authors' reputations.
|
49
|
+
|
50
|
+
Finally, any free program is threatened constantly by software
|
51
|
+
patents. We wish to avoid the danger that redistributors of a free
|
52
|
+
program will individually obtain patent licenses, in effect making the
|
53
|
+
program proprietary. To prevent this, we have made it clear that any
|
54
|
+
patent must be licensed for everyone's free use or not licensed at all.
|
55
|
+
|
56
|
+
The precise terms and conditions for copying, distribution and
|
57
|
+
modification follow.
|
58
|
+
|
59
|
+
GNU GENERAL PUBLIC LICENSE
|
60
|
+
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
61
|
+
|
62
|
+
0. This License applies to any program or other work which contains
|
63
|
+
a notice placed by the copyright holder saying it may be distributed
|
64
|
+
under the terms of this General Public License. The "Program", below,
|
65
|
+
refers to any such program or work, and a "work based on the Program"
|
66
|
+
means either the Program or any derivative work under copyright law:
|
67
|
+
that is to say, a work containing the Program or a portion of it,
|
68
|
+
either verbatim or with modifications and/or translated into another
|
69
|
+
language. (Hereinafter, translation is included without limitation in
|
70
|
+
the term "modification".) Each licensee is addressed as "you".
|
71
|
+
|
72
|
+
Activities other than copying, distribution and modification are not
|
73
|
+
covered by this License; they are outside its scope. The act of
|
74
|
+
running the Program is not restricted, and the output from the Program
|
75
|
+
is covered only if its contents constitute a work based on the
|
76
|
+
Program (independent of having been made by running the Program).
|
77
|
+
Whether that is true depends on what the Program does.
|
78
|
+
|
79
|
+
1. You may copy and distribute verbatim copies of the Program's
|
80
|
+
source code as you receive it, in any medium, provided that you
|
81
|
+
conspicuously and appropriately publish on each copy an appropriate
|
82
|
+
copyright notice and disclaimer of warranty; keep intact all the
|
83
|
+
notices that refer to this License and to the absence of any warranty;
|
84
|
+
and give any other recipients of the Program a copy of this License
|
85
|
+
along with the Program.
|
86
|
+
|
87
|
+
You may charge a fee for the physical act of transferring a copy, and
|
88
|
+
you may at your option offer warranty protection in exchange for a fee.
|
89
|
+
|
90
|
+
2. You may modify your copy or copies of the Program or any portion
|
91
|
+
of it, thus forming a work based on the Program, and copy and
|
92
|
+
distribute such modifications or work under the terms of Section 1
|
93
|
+
above, provided that you also meet all of these conditions:
|
94
|
+
|
95
|
+
a) You must cause the modified files to carry prominent notices
|
96
|
+
stating that you changed the files and the date of any change.
|
97
|
+
|
98
|
+
b) You must cause any work that you distribute or publish, that in
|
99
|
+
whole or in part contains or is derived from the Program or any
|
100
|
+
part thereof, to be licensed as a whole at no charge to all third
|
101
|
+
parties under the terms of this License.
|
102
|
+
|
103
|
+
c) If the modified program normally reads commands interactively
|
104
|
+
when run, you must cause it, when started running for such
|
105
|
+
interactive use in the most ordinary way, to print or display an
|
106
|
+
announcement including an appropriate copyright notice and a
|
107
|
+
notice that there is no warranty (or else, saying that you provide
|
108
|
+
a warranty) and that users may redistribute the program under
|
109
|
+
these conditions, and telling the user how to view a copy of this
|
110
|
+
License. (Exception: if the Program itself is interactive but
|
111
|
+
does not normally print such an announcement, your work based on
|
112
|
+
the Program is not required to print an announcement.)
|
113
|
+
|
114
|
+
These requirements apply to the modified work as a whole. If
|
115
|
+
identifiable sections of that work are not derived from the Program,
|
116
|
+
and can be reasonably considered independent and separate works in
|
117
|
+
themselves, then this License, and its terms, do not apply to those
|
118
|
+
sections when you distribute them as separate works. But when you
|
119
|
+
distribute the same sections as part of a whole which is a work based
|
120
|
+
on the Program, the distribution of the whole must be on the terms of
|
121
|
+
this License, whose permissions for other licensees extend to the
|
122
|
+
entire whole, and thus to each and every part regardless of who wrote it.
|
123
|
+
|
124
|
+
Thus, it is not the intent of this section to claim rights or contest
|
125
|
+
your rights to work written entirely by you; rather, the intent is to
|
126
|
+
exercise the right to control the distribution of derivative or
|
127
|
+
collective works based on the Program.
|
128
|
+
|
129
|
+
In addition, mere aggregation of another work not based on the Program
|
130
|
+
with the Program (or with a work based on the Program) on a volume of
|
131
|
+
a storage or distribution medium does not bring the other work under
|
132
|
+
the scope of this License.
|
133
|
+
|
134
|
+
3. You may copy and distribute the Program (or a work based on it,
|
135
|
+
under Section 2) in object code or executable form under the terms of
|
136
|
+
Sections 1 and 2 above provided that you also do one of the following:
|
137
|
+
|
138
|
+
a) Accompany it with the complete corresponding machine-readable
|
139
|
+
source code, which must be distributed under the terms of Sections
|
140
|
+
1 and 2 above on a medium customarily used for software interchange; or,
|
141
|
+
|
142
|
+
b) Accompany it with a written offer, valid for at least three
|
143
|
+
years, to give any third party, for a charge no more than your
|
144
|
+
cost of physically performing source distribution, a complete
|
145
|
+
machine-readable copy of the corresponding source code, to be
|
146
|
+
distributed under the terms of Sections 1 and 2 above on a medium
|
147
|
+
customarily used for software interchange; or,
|
148
|
+
|
149
|
+
c) Accompany it with the information you received as to the offer
|
150
|
+
to distribute corresponding source code. (This alternative is
|
151
|
+
allowed only for noncommercial distribution and only if you
|
152
|
+
received the program in object code or executable form with such
|
153
|
+
an offer, in accord with Subsection b above.)
|
154
|
+
|
155
|
+
The source code for a work means the preferred form of the work for
|
156
|
+
making modifications to it. For an executable work, complete source
|
157
|
+
code means all the source code for all modules it contains, plus any
|
158
|
+
associated interface definition files, plus the scripts used to
|
159
|
+
control compilation and installation of the executable. However, as a
|
160
|
+
special exception, the source code distributed need not include
|
161
|
+
anything that is normally distributed (in either source or binary
|
162
|
+
form) with the major components (compiler, kernel, and so on) of the
|
163
|
+
operating system on which the executable runs, unless that component
|
164
|
+
itself accompanies the executable.
|
165
|
+
|
166
|
+
If distribution of executable or object code is made by offering
|
167
|
+
access to copy from a designated place, then offering equivalent
|
168
|
+
access to copy the source code from the same place counts as
|
169
|
+
distribution of the source code, even though third parties are not
|
170
|
+
compelled to copy the source along with the object code.
|
171
|
+
|
172
|
+
4. You may not copy, modify, sublicense, or distribute the Program
|
173
|
+
except as expressly provided under this License. Any attempt
|
174
|
+
otherwise to copy, modify, sublicense or distribute the Program is
|
175
|
+
void, and will automatically terminate your rights under this License.
|
176
|
+
However, parties who have received copies, or rights, from you under
|
177
|
+
this License will not have their licenses terminated so long as such
|
178
|
+
parties remain in full compliance.
|
179
|
+
|
180
|
+
5. You are not required to accept this License, since you have not
|
181
|
+
signed it. However, nothing else grants you permission to modify or
|
182
|
+
distribute the Program or its derivative works. These actions are
|
183
|
+
prohibited by law if you do not accept this License. Therefore, by
|
184
|
+
modifying or distributing the Program (or any work based on the
|
185
|
+
Program), you indicate your acceptance of this License to do so, and
|
186
|
+
all its terms and conditions for copying, distributing or modifying
|
187
|
+
the Program or works based on it.
|
188
|
+
|
189
|
+
6. Each time you redistribute the Program (or any work based on the
|
190
|
+
Program), the recipient automatically receives a license from the
|
191
|
+
original licensor to copy, distribute or modify the Program subject to
|
192
|
+
these terms and conditions. You may not impose any further
|
193
|
+
restrictions on the recipients' exercise of the rights granted herein.
|
194
|
+
You are not responsible for enforcing compliance by third parties to
|
195
|
+
this License.
|
196
|
+
|
197
|
+
7. If, as a consequence of a court judgment or allegation of patent
|
198
|
+
infringement or for any other reason (not limited to patent issues),
|
199
|
+
conditions are imposed on you (whether by court order, agreement or
|
200
|
+
otherwise) that contradict the conditions of this License, they do not
|
201
|
+
excuse you from the conditions of this License. If you cannot
|
202
|
+
distribute so as to satisfy simultaneously your obligations under this
|
203
|
+
License and any other pertinent obligations, then as a consequence you
|
204
|
+
may not distribute the Program at all. For example, if a patent
|
205
|
+
license would not permit royalty-free redistribution of the Program by
|
206
|
+
all those who receive copies directly or indirectly through you, then
|
207
|
+
the only way you could satisfy both it and this License would be to
|
208
|
+
refrain entirely from distribution of the Program.
|
209
|
+
|
210
|
+
If any portion of this section is held invalid or unenforceable under
|
211
|
+
any particular circumstance, the balance of the section is intended to
|
212
|
+
apply and the section as a whole is intended to apply in other
|
213
|
+
circumstances.
|
214
|
+
|
215
|
+
It is not the purpose of this section to induce you to infringe any
|
216
|
+
patents or other property right claims or to contest validity of any
|
217
|
+
such claims; this section has the sole purpose of protecting the
|
218
|
+
integrity of the free software distribution system, which is
|
219
|
+
implemented by public license practices. Many people have made
|
220
|
+
generous contributions to the wide range of software distributed
|
221
|
+
through that system in reliance on consistent application of that
|
222
|
+
system; it is up to the author/donor to decide if he or she is willing
|
223
|
+
to distribute software through any other system and a licensee cannot
|
224
|
+
impose that choice.
|
225
|
+
|
226
|
+
This section is intended to make thoroughly clear what is believed to
|
227
|
+
be a consequence of the rest of this License.
|
228
|
+
|
229
|
+
8. If the distribution and/or use of the Program is restricted in
|
230
|
+
certain countries either by patents or by copyrighted interfaces, the
|
231
|
+
original copyright holder who places the Program under this License
|
232
|
+
may add an explicit geographical distribution limitation excluding
|
233
|
+
those countries, so that distribution is permitted only in or among
|
234
|
+
countries not thus excluded. In such case, this License incorporates
|
235
|
+
the limitation as if written in the body of this License.
|
236
|
+
|
237
|
+
9. The Free Software Foundation may publish revised and/or new versions
|
238
|
+
of the General Public License from time to time. Such new versions will
|
239
|
+
be similar in spirit to the present version, but may differ in detail to
|
240
|
+
address new problems or concerns.
|
241
|
+
|
242
|
+
Each version is given a distinguishing version number. If the Program
|
243
|
+
specifies a version number of this License which applies to it and "any
|
244
|
+
later version", you have the option of following the terms and conditions
|
245
|
+
either of that version or of any later version published by the Free
|
246
|
+
Software Foundation. If the Program does not specify a version number of
|
247
|
+
this License, you may choose any version ever published by the Free Software
|
248
|
+
Foundation.
|
249
|
+
|
250
|
+
10. If you wish to incorporate parts of the Program into other free
|
251
|
+
programs whose distribution conditions are different, write to the author
|
252
|
+
to ask for permission. For software which is copyrighted by the Free
|
253
|
+
Software Foundation, write to the Free Software Foundation; we sometimes
|
254
|
+
make exceptions for this. Our decision will be guided by the two goals
|
255
|
+
of preserving the free status of all derivatives of our free software and
|
256
|
+
of promoting the sharing and reuse of software generally.
|
257
|
+
|
258
|
+
NO WARRANTY
|
259
|
+
|
260
|
+
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
|
261
|
+
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
|
262
|
+
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
|
263
|
+
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
|
264
|
+
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
265
|
+
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
266
|
+
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
|
267
|
+
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
|
268
|
+
REPAIR OR CORRECTION.
|
269
|
+
|
270
|
+
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
271
|
+
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
|
272
|
+
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
|
273
|
+
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
|
274
|
+
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
|
275
|
+
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
|
276
|
+
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
|
277
|
+
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
|
278
|
+
POSSIBILITY OF SUCH DAMAGES.
|
279
|
+
|
280
|
+
END OF TERMS AND CONDITIONS
|
281
|
+
|
282
|
+
How to Apply These Terms to Your New Programs
|
283
|
+
|
284
|
+
If you develop a new program, and you want it to be of the greatest
|
285
|
+
possible use to the public, the best way to achieve this is to make it
|
286
|
+
free software which everyone can redistribute and change under these terms.
|
287
|
+
|
288
|
+
To do so, attach the following notices to the program. It is safest
|
289
|
+
to attach them to the start of each source file to most effectively
|
290
|
+
convey the exclusion of warranty; and each file should have at least
|
291
|
+
the "copyright" line and a pointer to where the full notice is found.
|
292
|
+
|
293
|
+
{description}
|
294
|
+
Copyright (C) {year} {fullname}
|
295
|
+
|
296
|
+
This program is free software; you can redistribute it and/or modify
|
297
|
+
it under the terms of the GNU General Public License as published by
|
298
|
+
the Free Software Foundation; either version 2 of the License, or
|
299
|
+
(at your option) any later version.
|
300
|
+
|
301
|
+
This program is distributed in the hope that it will be useful,
|
302
|
+
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
303
|
+
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
304
|
+
GNU General Public License for more details.
|
305
|
+
|
306
|
+
You should have received a copy of the GNU General Public License along
|
307
|
+
with this program; if not, write to the Free Software Foundation, Inc.,
|
308
|
+
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
309
|
+
|
310
|
+
Also add information on how to contact you by electronic and paper mail.
|
311
|
+
|
312
|
+
If the program is interactive, make it output a short notice like this
|
313
|
+
when it starts in an interactive mode:
|
314
|
+
|
315
|
+
Gnomovision version 69, Copyright (C) year name of author
|
316
|
+
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
317
|
+
This is free software, and you are welcome to redistribute it
|
318
|
+
under certain conditions; type `show c' for details.
|
319
|
+
|
320
|
+
The hypothetical commands `show w' and `show c' should show the appropriate
|
321
|
+
parts of the General Public License. Of course, the commands you use may
|
322
|
+
be called something other than `show w' and `show c'; they could even be
|
323
|
+
mouse-clicks or menu items--whatever suits your program.
|
324
|
+
|
325
|
+
You should also get your employer (if you work as a programmer) or your
|
326
|
+
school, if any, to sign a "copyright disclaimer" for the program, if
|
327
|
+
necessary. Here is a sample; alter the names:
|
328
|
+
|
329
|
+
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
|
330
|
+
`Gnomovision' (which makes passes at compilers) written by James Hacker.
|
331
|
+
|
332
|
+
{signature of Ty Coon}, 1 April 1989
|
333
|
+
Ty Coon, President of Vice
|
334
|
+
|
335
|
+
This General Public License does not permit incorporating your program into
|
336
|
+
proprietary programs. If your program is a subroutine library, you may
|
337
|
+
consider it more useful to permit linking proprietary applications with the
|
338
|
+
library. If this is what you want to do, use the GNU Lesser General
|
339
|
+
Public License instead of this License.
|
data/README.md
ADDED
@@ -0,0 +1,204 @@
|
|
1
|
+
# cloudformation-tool
|
2
|
+
|
3
|
+
A pre-compiler for CloudFormation YAML files, allowing modularization of large CloudFormation
|
4
|
+
templates.
|
5
|
+
|
6
|
+
By breaking a large template into distinct modules, including allowing parts to be
|
7
|
+
loaded from git submodules or even to be downloaded on the fly, very large CloudFormation
|
8
|
+
configurations become manageable and useful.
|
9
|
+
|
10
|
+
## Syntax
|
11
|
+
|
12
|
+
This tool is based on the CloudFormation YAML syntax (as it is a bit more human friendly than
|
13
|
+
the original JSON syntax) and extend it with a few more operation to allow for the
|
14
|
+
modularization of templates. The following additional syntaxes are supported:
|
15
|
+
|
16
|
+
### Including Additional Sub-templates
|
17
|
+
|
18
|
+
The CloudFormation pre-compiler introduces a new top-level element called `Include`.
|
19
|
+
|
20
|
+
This element specifies a list of additional template files to be loaded and merged into
|
21
|
+
the current template file.
|
22
|
+
|
23
|
+
Loading is done using the same file resolution rules as the
|
24
|
+
`compile` CLI command:
|
25
|
+
- resolution is done relative to the directory of the current file
|
26
|
+
- if the path specified is missing the `.yaml` extension and a valid file with the extension
|
27
|
+
exist, it will be loaded instead.
|
28
|
+
- if the path specified is a directory, the file `cloud-formation.yaml` will be loaded
|
29
|
+
from that directory
|
30
|
+
|
31
|
+
The merged file must be a valid CloudFormation template - it should have at least a top-level
|
32
|
+
`Resources` entry and can have any other top-level entry that a standard CloudFormation
|
33
|
+
template can include (see below regarding the merging of parameters). The sub-template will
|
34
|
+
be merged back to the top template without nesting - e.g. all resources specified in a
|
35
|
+
sub-template are standard resources in the top-level `Resources` list.
|
36
|
+
|
37
|
+
As logical resource names as well as parameters are merged into a single name space, these
|
38
|
+
can be referenced directly from any file. Unless as specified for parameter merging below, the
|
39
|
+
names used can be directly addressed as done in a normal CloudFormation template.
|
40
|
+
|
41
|
+
#### Parameter merging
|
42
|
+
|
43
|
+
A sub-template may specify parameters just like a standard CloudFormation template, and as
|
44
|
+
long as each parameter is specified uniquely (i.e. only once) in the entire set of sub-templates
|
45
|
+
that are being loaded, then they are just merged into a flat list and all parameters can be
|
46
|
+
used equally from all sub-templates.
|
47
|
+
|
48
|
+
If the same parameter name is mentioned in more than one file, then special merging rules take
|
49
|
+
effect:
|
50
|
+
1. If the same parameter is named in more than one file, and in all instances the default
|
51
|
+
value is exactly the same, than the merging is done normally - we basically ignore the
|
52
|
+
duplicate settings.
|
53
|
+
1. If the same parameter is named in more than one file, and uses different default value,
|
54
|
+
then the new parameter is renamed using a path-specific template (i.e. based on the path
|
55
|
+
to the sub-template where the new copy was encountered) and any use of that parameter in
|
56
|
+
the current sub-template is also renamed automatically, as if there is full scoping of the
|
57
|
+
nested sub-template (though the mangled name is not very readable due to YAML restrictions
|
58
|
+
on the available characters for names). Uses of the duplicate parameter in sub-templates
|
59
|
+
other than the one where it was defined should use the mangled form if they mean the new
|
60
|
+
parameter or the original form if they mean the original parameter
|
61
|
+
|
62
|
+
#### Example:
|
63
|
+
|
64
|
+
```
|
65
|
+
AWSTemplateFormatVersion: "2010-09-09"
|
66
|
+
Description: "Example cloud formation template"
|
67
|
+
Parameters:
|
68
|
+
DomainName:
|
69
|
+
Description: "The DNS domain name for the system"
|
70
|
+
Type: String
|
71
|
+
Default: example.com
|
72
|
+
AMI:
|
73
|
+
Description: "The AMI ID for the image to deploy"
|
74
|
+
Type: String
|
75
|
+
Default: ami-af4333cf
|
76
|
+
|
77
|
+
Resources:
|
78
|
+
VPC:
|
79
|
+
Type: AWS::EC2::VPC
|
80
|
+
Properties:
|
81
|
+
CidrBlock: 172.20.0.0/16
|
82
|
+
EnableDnsSupport: true
|
83
|
+
EnableDnsHostnames: true
|
84
|
+
SecurityGroupExample:
|
85
|
+
Type: AWS::EC2::SecurityGroup
|
86
|
+
Properties:
|
87
|
+
VpcId: !Ref VPC
|
88
|
+
GroupDescription: example security group
|
89
|
+
SecurityGroupIngress:
|
90
|
+
- { IpProtocol: icmp, CidrIp: 0.0.0.0/0, FromPort: -1, ToPort: -1 }
|
91
|
+
- { IpProtocol: tcp, CidrIp: 0.0.0.0/0, FromPort: 22, ToPort: 22 }
|
92
|
+
|
93
|
+
Include:
|
94
|
+
- network
|
95
|
+
- servers/global
|
96
|
+
- outputs.yaml
|
97
|
+
```
|
98
|
+
|
99
|
+
#### Logical resource merging
|
100
|
+
|
101
|
+
Logical resources are not mangled - if multiple resources with the same name are defined in
|
102
|
+
multiple sub-templates, this is an error that would cause the tool to abort.
|
103
|
+
|
104
|
+
### Loading user data files
|
105
|
+
|
106
|
+
When specifying a user-data block for a `LaunchConfiguration` resource or an `Instance`
|
107
|
+
resource, the user-data can be loaded from an external YAML file (only YAML formatted user-data
|
108
|
+
is currently supported, sorry) by specifying the `UserData` element as a map with the single
|
109
|
+
field `File` that is set with the relative path to the user-data file. The user-data file is
|
110
|
+
expected to be a cloud-init file with the extension `.init`.
|
111
|
+
|
112
|
+
The loaded file will be checked that it does not exceed the user-data size limitation. If the
|
113
|
+
file is bigger than can fit in the AWS user-data block, it will first be compressed using gzip
|
114
|
+
and if it is still too large, it will be uploaded to S3 and the user-data block will be set
|
115
|
+
with a cloud-init download reference to the S3 object.
|
116
|
+
|
117
|
+
#### Example:
|
118
|
+
|
119
|
+
```
|
120
|
+
LaunchConfigurationForServer:
|
121
|
+
Type: AWS::AutoScaling::LaunchConfiguration
|
122
|
+
Properties:
|
123
|
+
AssociatePublicIpAddress: true
|
124
|
+
IamInstanceProfile: !Ref InstanceProfileForServer
|
125
|
+
ImageId: !Ref AMI # read from parameters
|
126
|
+
InstanceType: !Ref InstanceType # read from parameters
|
127
|
+
KeyName: !Ref KeyName # read from parameters
|
128
|
+
SecurityGroups:
|
129
|
+
- Ref: SecurityGroupExample
|
130
|
+
UserData:
|
131
|
+
File: config.init
|
132
|
+
```
|
133
|
+
|
134
|
+
### Loading Lambda code
|
135
|
+
|
136
|
+
When specifying the `Code` property of a `AWS::Lambda::Function` resource, instead of
|
137
|
+
specifying the S3 bucket and object key, the field `URL` may be used to specify an HTTP URL
|
138
|
+
from which the code is to be uploaded to AWS Lambda. The tool will download the code file from
|
139
|
+
the specified URL, upload it to S3 and specify the correct S3 location for CloudFormation.
|
140
|
+
|
141
|
+
In the future we plan to add support for specifying `File` to upload from a local file.
|
142
|
+
|
143
|
+
#### Example:
|
144
|
+
|
145
|
+
```
|
146
|
+
LambdaExample:
|
147
|
+
Type: AWS::Lambda::Function
|
148
|
+
Properties:
|
149
|
+
FunctionName: !Join [ "-", [ route53-update, !Ref SystemTag ] ]
|
150
|
+
Runtime: java8
|
151
|
+
Code:
|
152
|
+
URL: https://github.com/GreenfieldTech/lambda-route53-updates/releases/download/0.2.5/lambda-route53-updates-0.2.5.jar
|
153
|
+
Description: Update DNS with autoscaling servers
|
154
|
+
MemorySize: 256
|
155
|
+
Timeout: 60
|
156
|
+
Handler: net.gftc.aws.route53.NotifyRecords
|
157
|
+
Environment:
|
158
|
+
Variables: # set variables here, see lambda-route53-updates for documentation ...
|
159
|
+
Role: !GetAtt [ LambdaExecutionRole, Arn ]
|
160
|
+
```
|
161
|
+
|
162
|
+
## Caching
|
163
|
+
|
164
|
+
Some resource compilation may require uploading to S3, such as Lambda code or cloud-init setup
|
165
|
+
files. In such cases, the tool will take precaution not to update the uploaded file (and thus
|
166
|
+
cause a CloudFormation update) unless the content has changed. This is done by comparing the
|
167
|
+
MD5 hash of the compiled object with the MD5 hash of the previously uploaded object, and
|
168
|
+
re-uploading and updating CloudFormation only if a change in the actual content as been
|
169
|
+
detected.
|
170
|
+
|
171
|
+
## Usage
|
172
|
+
|
173
|
+
The CloudFormation Tool uses a "sub-command CLI syntax" (like GIT, for example).
|
174
|
+
|
175
|
+
Usage: `cftool [options] <command> <command-options...>`
|
176
|
+
|
177
|
+
The following commands are supported:
|
178
|
+
|
179
|
+
- `list` - List names and status of existing CloudFormation stacks
|
180
|
+
- `parameters` - List parameters defined in the specified CloudFormation template and
|
181
|
+
their default values.
|
182
|
+
- `compile` - Compile a CloudFormation template set (including all caching needed) and
|
183
|
+
output the resulting valid CloudFormation template to the console.
|
184
|
+
- `create` - Create or update a CloudFormation stack by compiling the specified template
|
185
|
+
set and uploading it to CloudFormation. If no stack with the specified name exists, then
|
186
|
+
a new stack will be created, otherwise the existing stack will be updated. After sending the
|
187
|
+
template to CloudFormation, the tool will immediately start `monitor` mode until the
|
188
|
+
operation has completed successfully or with an error.
|
189
|
+
- `monitor` - Track and display ongoing events for the named stack.
|
190
|
+
- `status` - Check if the names stack exists or not
|
191
|
+
- `delete` - Delete the specified stack. After issuing the delete command, the tool will
|
192
|
+
immediately start `monitor` mode until the operation has completed.
|
193
|
+
- `servers` - List EC2 instances created and managed by this stack.
|
194
|
+
|
195
|
+
Please see the specific help for each command by running `cftool <command> --help` for
|
196
|
+
more details and specific options.
|
197
|
+
|
198
|
+
### Region Selection
|
199
|
+
|
200
|
+
The AWS region to be used can be select by specifying top level option (i.e. before the command name) `-r <region>`, by providing the standard environment variable `AWS_DEFAULT_REGION` or it will default to `us-west-1`
|
201
|
+
|
202
|
+
### Credentials Selection
|
203
|
+
|
204
|
+
The tool will use the standard AWS credentials selection process, except when you want to use AWS CLI configured credential profiles, you may select to use a profile other than "default" by specifying the top level option (i.e. before the command name) `-p <profile>`, by providing the standard environment variable `AWS_DEFAULT_PROFILE` or by having a file called `.awsprofile` - whose content is the name of a valid AWS REGION - in a parent directory (at any level up to the root directory).
|