├── LICENSE
├── README.md
└── azurerm_example_main.tf
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 |
635 | Copyright (C)
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Copyright (C)
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Terraform Guide
2 |
3 | > [!WARNING]
4 | > This is an advanced guide and assumes you already know the basics of Terraform. Think of this more like an advanced cheat sheet. I went through various sources, captured any notes that I felt were important, and organized them into the README file you see here. If you are new to Terraform, then I would suggest first going through the [HashiCorp Docs](https://www.terraform.io/docs) or doing a couple [HashiCorp Learn](https://learn.hashicorp.com/) courses.
5 |
6 | > [!NOTE]
7 | > Terraform comes in a few different versions. This guide covers Terraform "*Open Source*" only. It doesn't cover Terraform "*Cloud*" or Terraform "*Enterprise*".
8 |
9 | > [!IMPORTANT]
10 | This is a live document. Some of the sections are still a work in progress. I will be continually updating it over time.
11 |
12 | ---
13 |
14 | # Table of Contents
15 |
16 | Part 1 - Terraform Files, Folder Structure, and Blocks
17 | - [Configuration Files](README.md#configuration-files)
18 | - [Root Module](README.md#root-module)
19 | - [Folder Structure](README.md#typical-root-module-folder-structure)
20 | - [terraform Block](README.md#terraform-block)
21 | - [provider Blocks](README.md#provider-configuration-blocks)
22 | - [terraform init](README.md#terraform-init)
23 |
24 | Part 2 - Terraform State
25 | - [State Files](README.md#state-files)
26 | - [Local Backend](README.md#local-backend)
27 | - [Remote Backend](README.md#remote-backend)
28 | - [Terraform Workspaces](README.md#terraform-workspaces)
29 |
30 | Part 3 - Terraform Code
31 | - [Input Variables](README.md#input-variables-aka-variables)
32 | - [Local Values](README.md#local-values-aka-locals)
33 | - [Data Sources](README.md#data-sources)
34 | - [Resources](README.md#resources)
35 | - [Child Modules](README.md#child-modules-aka-modules)
36 | - [Output Variables](README.md#output-variables-aka-outputs)
37 |
38 | Part 4 - Everything Else
39 | - [Syntax Notes](README.md#syntax-notes)
40 | - [Loops (count and for_each)](README.md#loops)
41 | - [For Expressions](README.md#for-expressions)
42 | - [String Directives](README.md#string-directives)
43 | - [Lifecycle Settings](README.md#lifecycle-settings)
44 | - [Terraform CLI Commands](README.md#terraform-cli-commands)
45 | - [.gitignore File](README.md#gitignore-file)
46 |
47 | ---
48 |
49 | ## Terraform Files, Folder Structure, and Common Code Blocks
50 |
51 | ### Configuration Files
52 | - Files that contain Terraform code are officially called *configuration files*
53 | - Configuration Files can be written in two different formats:
54 | - native format which uses the `.tf` file extension
55 | - alternate JSON format which uses the `.tf.json` file extension
56 | - This guide will only focus on the native format
57 |
58 | ### Root Module
59 | - When you run Terraform commands such as `terraform plan` or `terraform apply` you run it against a directory of Configuration Files. This directory could contain one Configuration File, or it could contain many
60 | - Separating your Terraform code into multiple Configuration Files is totally optional and for you to decide. Using multiple Configuration Files can make it easier for readers and maintainers of your code
61 | - Terraform will automatically evaluate ALL Configuration Files found in the **top level** of the directory you run it against
62 | - This top-level directory is commonly referred to as the *Root Module*
63 |
64 | ### Typical Root Module Folder Structure
65 | - `main.tf`
66 | - Contains all of your `locals` blocks, `resource` blocks, `module` blocks, `data` blocks
67 | - `outputs.tf`
68 | - Contains all of your `output` blocks
69 | - `variables.tf`
70 | - Contains all of your `variable` blocks
71 | - `versions.tf`, `terraform.tf`, `providers.tf`
72 | - Recently, it has been common to put the `terraform` configuration block and all of your `provider` configuration blocks into separate Configuration Files
73 | - Some of the common filenames that I've seen used for this are `versions.tf`, `terraform.tf`, or `providers.tf`
74 | - You may not always find these files. If they don't exist, then these blocks are typically found in `main.tf` instead
75 | - `dependencies.tf`
76 | - Another fairly recent practice is to put all of your `data` blocks (data sources) into this separate Configuration File
77 | - Same as above, you may not always find this file, and if not, the `data` blocks are typically found in `main.tf` instead
78 |
79 | ### terraform block
80 | ```terraform
81 | # ROOT MODULE ONLY
82 | terraform {
83 |
84 | required_version = "=1.2.0"
85 |
86 | required_providers {
87 | azurerm = {
88 | source = "hashicorp/azurerm"
89 | version = "=3.7.0"
90 | }
91 | aws = {
92 | source = "hashicorp/aws"
93 | version = "=4.18.0"
94 | }
95 | }
96 |
97 | backend "azurerm" {
98 | resource_group_name = "value"
99 | storage_account_name = "value"
100 | }
101 |
102 | }
103 |
104 | # CHILD MODULE ONLY
105 | terraform {
106 |
107 | required_version = ">= 1.0.0" # only specify minimum in child modules
108 |
109 | required_providers {
110 | aws = {
111 | source = "hashicorp/aws"
112 | version = ">=2.0.0" # only specify minimum in child modules
113 | configuration_aliases = [ aws.first, aws.second ]
114 | }
115 | }
116 |
117 | # no backend configurations in child modules
118 |
119 | }
120 | ```
121 | - The `terraform` block supports hard-coded values only
122 | - `required_version` is used to specify which version(s) of Terraform are supported by this module
123 | - You can specify an exact version, a min version, a max version, or even a range of versions. See the [Version Constraints](https://developer.hashicorp.com/terraform/language/expressions/version-constraints) documentation for more info
124 | - In Child Modules, you should only specify a minimum version. Let the Root Module specify the maximum version
125 | - `required_providers` declares which providers are used by this module, so that Terraform can install and use these Providers
126 | - In Root Modules:
127 | - You should include all Providers being used by the Root Module plus any Child Modules being called
128 | - In Child Modules:
129 | - You only need to include Providers being used by that Child Module
130 | - You should only specify a minimum version. Let the Root Module specify the maximum version
131 | - If your Child Module uses multiple copies of the same Provider, then specify the `configuration_aliases` argument, this specifies the exact Providers and their Aliases that must be passed to this Child Module when calling it
132 | - `backend` is used to configure which Backend the Terraform CLI will use
133 | - This block only belongs in Root Modules
134 | - The `terraform` block has a few other uses, but they will not be covered here. Read the [Terraform Settings](https://www.terraform.io/language/settings) docs for more info
135 |
136 | ### provider Configuration Blocks
137 | ```terraform
138 | # ROOT MODULE ONLY
139 | provider "aws" {
140 | region = "us-east-1"
141 | }
142 |
143 | provider "aws" {
144 | alias = "second"
145 | region = "us-west-2"
146 | }
147 |
148 | provider "azurerm" {
149 | # version = "1.0" # DEPRECATED! DO NOT USE!
150 | features {}
151 | }
152 |
153 | provider "google" {
154 | project = "acme-app"
155 | region = "us-central1"
156 | }
157 | ```
158 | - Each Provider has its own unique settings. This may include things such as the credentials used to authenticate to the vendor's API, which region to use, which subscription to use, etc.
159 | - Do not put sensitive credentials in the `provider` block. Passwords stored directly in code are **bad**!
160 | - Some Providers support alternate ways to provide these values, such as using environment variables. It is recommended to use these alternate methods
161 | - Check out your Provider's documentation for more information
162 | - You may still see code that uses the `version` argument inside of a `provider` block. Do NOT use this, it's deprecated. Instead, you should specify the supported Provider versions in the `terraform` block (see above)
163 | - You can declare multiple `provider` blocks for a single Provider, with each block using a different configuration. See the two `aws` blocks in the example code above
164 | - The first instance you define is considered the *default* Provider and does not need to use the `alias` argument
165 | - Any other instances you define must have a unique `alias` argument that will be used to reference this instance of the Provider
166 | - `provider` configuration blocks go in the Root Module ONLY, they should NOT exist in Child Modules
167 | - Child Modules recieve their provider configurations from the Root Module
168 |
169 | ### terraform init
170 | You must run `terraform init` at least once before you can run any `plan` or `apply` commands. The `terraform init` command is a powerful command that has 3 different purposes:
171 |
172 | 1 - Configures your Providers
173 | - It looks at your Configuration Files, figures out which Providers your code uses, and then automatically downloads those Providers into the `.terraform` folder
174 | - It will automatically create a lock file named `.terraform.lock.hcl`
175 | - The lock file stores the exact versions of the Providers that were downloaded by `init`
176 | - You should store this file in version control along with your code. This way everyone will use the same lock file and as a result everyone will download the same Provider versions
177 | - How do you upgrade to a new Provider version? First, upgrade the Provider version in the `terraform.required_providers` block and then run `terraform init -upgrade`. This will download the new Provider and it will automatically update the `.terraform.lock.hcl` file as well
178 | - Any time you add a new Provider to your code you will need to run `terraform init` again in order to download that Provider
179 |
180 | 2 - Initializes your chosen Backend
181 | - Any time you change to a different Backend you will need to run `terraform init` again in order to initialize the new Backend
182 |
183 | 3 - Configures your Modules
184 | - Any time you add a Module to your Configuration Files, or you change the source of an existing Module, you will need to run `terraform init` again
185 |
186 | ---
187 |
188 | # Terraform State
189 |
190 | ### State Files
191 | - State Files use a custom JSON format
192 | - You should NEVER manually edit State Files. Instead, use commands like `terraform import` and `terraform state` to modify the state
193 | - You should NEVER store your State Files in Version Control Systems like Git:
194 | - State Files are stored in plain text, and they often include passwords and other sensitive information
195 | - Make sure your State Files are stored in a secure location and accessible only by users or accounts who require access
196 |
197 | ### Local Backend
198 | - This is the default backend that Terraform will use unless you specify a different backend
199 | - This will be created as a file named `terraform.tfstate` in the Root Module
200 | - Problems with a Local Backend:
201 | - The State File is local to your computer and can not be shared by other teammates
202 | - You can only use 1 local State File
203 | - (Workspaces are an exception, but they are not recommended)
204 | - You can start with a Local Backend, and later you can change your code to use a Remote Backend. Terraform will recognize the local State File and prompt you to copy it to the new Remote Backend
205 |
206 | ### Remote Backend
207 | - You can only configure 1 Remote Backend per Root Module
208 | - Configuring a Remote Backend is done in the `backend` block inside the `terraform` block:
209 | ```terraform
210 | terraform {
211 | backend "azurerm" {
212 | key1 = value1
213 | key2 = value2
214 | key3 = value3
215 | }
216 | }
217 | ```
218 | - Remote Backends require configuration parameters, which specify:
219 | - How to find the storage (name, resource group, etc.)
220 | - How to authenticate to the storage (service principal, access key, etc.)
221 | - Read your Remote Backend's documentation for for more info
222 | - `backend` blocks can NOT use Terraform variables or references, they must use hard-coded values
223 | - This is because Terraform sets the Remote Backend as its very first step, even before it processes variables
224 | - Do NOT put sensitive values directly in the `backend` block. Passwords in code are bad!
225 | - You can remove some or all of the key/value pairs from the `backend` block and provide them in other ways:
226 | - Option 1 is individual key/value pairs: `terraform.exe -backend-config="key=value" -backend-config="key=value"`
227 | - Option 2 is to use a separate file: `terraform.exe -backend-config=backend.hcl`
228 | - Where `backend.hcl` is a file which contains only the key/value pairs that are needed by the backend
229 | - If this file contains sensitive values, then do NOT check it into version control
230 | - Option 3 is using environment variables supported by your Backend. Each Backend supports its own special environment variables. Check your Backend's documentation for more information
231 | - This is the preferred option, as credentials are kept out of your code
232 |
233 | ### Terraform Workspaces
234 | - Note: These are different from Terraform "Cloud" Workspaces
235 | - If you create Workspaces, they each get their own State File. However, all Workspaces will still share the same Backend
236 | - State Files for Workspaces are placed in a new subfolder called `env:` and each Workspace gets its own subfolder under that:
237 | - `\env:\workspace1\terraform.tfstate`
238 | - `\env:\workspace2\terraform.tfstate`
239 | - Switching Workspaces is equivalent to changing the path where your State File is stored
240 | - In general, these are confusing. It can be easy to mix up Workspaces and forget which one you are currently working on
241 | - If possible, stay away from using these!
242 |
243 | ---
244 |
245 | # Input Variables (aka Variables)
246 |
247 | ```terraform
248 | # defining a variable
249 | # remember, this is typically done inside a variables.tf file
250 | variable "exampleVarName" {
251 | description = "put a good description here"
252 | type = string | number | bool | list | tuple | set | map | object | any
253 | default = set a default value here
254 | sensitive = true # supported in Terraform 0.14.0 and later
255 | nullable = false # supported in Terraform 1.1.0 and later
256 |
257 | # supported in Terraform 0.13.0 and later
258 | validation {
259 | condition = var.exampleVarName > 10
260 | error_message = "your value needs to be greater than 10"
261 | }
262 | }
263 |
264 | # use a variable by prefixing the variable's name with var.
265 | var.exampleVarName
266 | ```
267 | - When defining a Variable, all parameters are optional
268 | - If `type` is omitted, then the default is `any`
269 | - If `sensitive` is omitted, then the default is `false`
270 | - If `nullable` is omitted, then the default is `true`
271 | - `type` can be a combination of different options: `list(number)`
272 | - `sensitive = true` prevents showing the value in any `plan` or `apply` commands
273 | - `nullable = false` ensures the value can never be set to `null`
274 | - `validation` blocks
275 | - You can have multiple `validation` blocks pers variable
276 | - `condition` is any condition that resolves to true or false. You can only test against this particular variable and nothing else
277 | - `error_message` is a message that is displayed if the condition is false
278 |
279 | ### How to set values for your Variables:
280 | 1. You can set a `default` value inside the Variable definition
281 | 2. Set an environment variable with the name of `TF_VAR_` and the value that you want to use
282 | - Linux: `export TF_VAR_varName=value`
283 | - PowerShell: `$env:TF_VAR_varName = 'value'`
284 | 3. Use a file with a `.tfvars` extension that lists Variable names and their values
285 | - Option 1: Terraform will automatically load your file if it is placed in your Root Module and it is named `terraform.tfvars` or `*.auto.tfvars`
286 | - Option 2: Pass your tfvars file with the `-var-file` switch: `terraform.exe plan -var-file=somefile.tfvars`
287 | 4. Pass a value with the `-var` switch: `terraform plan -var "name=value"`
288 | 5. If not set by any other method, then Terraform will interactively prompt you for a value at runtime
289 |
290 | Values are loaded in the following order, with the later options taking precedence over earlier ones:
291 | 1. Environment Variables
292 | 2. `terraform.tfvars` files
293 | 3. `*.auto.tfvars` files
294 | 4. `-var` and `-var-file` options, in the order they are given on the commandline
295 |
296 | # Variable Types
297 |
298 | ### Strings
299 | Represented by characters surrounded by double-quotes: `"this is a string"`
300 |
301 | Heredoc / Multi-line Strings
302 | ```terraform
303 | user_data = <<-EOT
304 | indented multi-line
305 | strings will go here
306 | EOT
307 |
308 | user_data = <
439 | # Where `attribute` is specific to the resource that is being fetched by the data source
440 | # In this case it could be id, location, account_kind, etc.
441 | ```
442 | - Data Sources fetch up-to-date information from your Providers (Azure, AWS, etc.) each time you run Terraform
443 | - Each Provider has their own list of Data Sources that they support
444 | - All Data Sources are Read-Only!
445 | - When defining a Data Source, the argument(s) that you specify can be thought of like search filters to limit what data is returned
446 | - Data Sources support `precondition` and `postcondition` blocks as well (WIP)
447 |
448 | ## Other types of Data Sources
449 | Click to expand
450 |
451 | ### Remote State Data Source
452 | - Use these when you want to pull info from a foreign Terraform State File
453 | - That foreign Terraform State must have some `outputs` already configured, because that's the information you're pulling from
454 |
455 | ```terraform
456 | # Defining a Remote State Data Source
457 | data "terraform_remote_state" "symbolicName" {
458 | backend = "azurerm"
459 | config = {
460 | key1 = value1
461 | key2 = value2
462 | }
463 | }
464 |
465 | # Using a Remote State Data Source:
466 | `data.teraform_remote_state.symbolicName.outputs.someOutputName`
467 | ```
468 | - In the `config` block you specify the storage and state file to connect to, as well as how to authenticate to that storage. You can use the same parameters you used for the Remote Backend settings
469 | - Partial config is NOT supported for Remote State Data Sources
470 |
471 | ### External Data Source
472 | - Provides an interface between Terraform and an external program
473 | - Example:
474 | ```terraform
475 | data "external" "symbolicName" {
476 | program = ["python", "${path.module}/example-data-source.py"]
477 |
478 | query = {
479 | id = "abc123"
480 | }
481 | }
482 | ```
483 | - The `program` must read all of the data passed to it on stdin
484 | - The `program` must parse all of the data that's passed to it as a JSON object
485 | - The JSON object must contain the contents of the `query`
486 | - The `program` must produce a valid JSON object on stdout
487 | - The JSON object must have all of its values as Strings
488 | - On successful completion the `program` must exit with a status of zero
489 | - If there's an error
490 | - The `program` must exit with a non-zero status
491 | - It must print a human-readable error message (ideally a single line) to `stderr`
492 | - `stdout` is ignored for an error
493 | - Terraform will re-run `program` each time that state is refreshed
494 | - `program` is of Type list(string)
495 | - First element is the program to run, and subsequent elements are optional commandline arguments
496 | - Terraform does not execute the program through a shell, so it is not necessary to escape shell metacharacters nor add quotes around arguments containing spaces
497 | - `query` is of Type map(string)
498 | - Optional
499 | - These values are passed to the program as query arguments
500 | - How to reference the data created from the external data source:
501 | - `data.external.symbolicName.result.someAttribute`
502 | - in var.List :