@schemastore/cloudbuild 0.0.7 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/LICENSE +674 -21
  2. package/README.md +3 -1
  3. package/index.d.ts +167 -260
  4. package/package.json +3 -8
package/LICENSE CHANGED
@@ -1,21 +1,674 @@
1
- MIT License
2
-
3
- Copyright (c) Florian Imdahl. All rights reserved.
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE
1
+ GNU GENERAL PUBLIC LICENSE
2
+ Version 3, 29 June 2007
3
+
4
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
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
+ <one line to give the program's name and a brief idea of what it does.>
635
+ Copyright (C) <year> <name of author>
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 <https://www.gnu.org/licenses/>.
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
+ <program> Copyright (C) <year> <name of author>
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
+ <https://www.gnu.org/licenses/>.
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
+ <https://www.gnu.org/licenses/why-not-lgpl.html>.
package/README.md CHANGED
@@ -5,8 +5,10 @@
5
5
  This package contains type definitions for cloudbuild.
6
6
 
7
7
  ## Details
8
+
8
9
  Files were exported from https://github.com/ffflorian/schemastore-updater/tree/main/schemas/cloudbuild.
9
10
 
10
11
  ## Additional Details
11
- * Last updated: Mon, Jan 23, 2023, 19:39:42 GMT
12
+
13
+ * Last updated: Fri, Mar 13, 2026, 11:19:37 GMT
12
14
  * Dependencies: none
package/index.d.ts CHANGED
@@ -1,28 +1,12 @@
1
1
  /* eslint-disable */
2
+
2
3
  /**
3
- * This file was automatically generated by json-schema-to-typescript.
4
- * DO NOT MODIFY IT BY HAND. Instead, modify the source JSONSchema file,
5
- * and run json-schema-to-typescript to regenerate this file.
4
+ * If set to true, automatically map all subsistutions and make them available as environment variables in a single step. If set to false, ignore substitutions for that step. Can be used for a build step or for an entire build.
6
5
  */
6
+ export type AutomapSubstitutions = boolean;
7
7
 
8
8
  /**
9
9
  * A build resource in the Cloud Build API.
10
- *
11
- * At a high level, a `Build` describes where to find source code, how to build
12
- * it (for example, the builder image to run on the source), and where to store
13
- * the built artifacts.
14
- *
15
- * Fields can include the following variables, which will be expanded when the
16
- * build is created:
17
- *
18
- * - $PROJECT_ID: the project ID of the build.
19
- * - $BUILD_ID: the autogenerated ID of the build.
20
- * - $REPO_NAME: the source repository name specified by RepoSource.
21
- * - $BRANCH_NAME: the branch name specified by RepoSource.
22
- * - $TAG_NAME: the tag name specified by RepoSource.
23
- * - $REVISION_ID or $COMMIT_SHA: the commit SHA specified by RepoSource or
24
- * resolved from the specified branch or tag.
25
- * - $SHORT_SHA: first 7 characters of $REVISION_ID or $COMMIT_SHA.
26
10
  */
27
11
  export interface GoogleCloudBuildBuildConfigFile {
28
12
  /**
@@ -30,383 +14,311 @@ export interface GoogleCloudBuildBuildConfigFile {
30
14
  */
31
15
  steps: BuildStep[];
32
16
  /**
33
- * Google Cloud Storage bucket where logs should be written (see
34
- * [Bucket Name
35
- * Requirements](https://cloud.google.com/storage/docs/bucket-naming#requirements)).
36
- * Logs file names will be of the format `${logs_bucket}/log-${build_id}.txt`.
17
+ * Google Cloud Storage bucket where logs should be written. Logs file names will be of the format ${logs_bucket}/log-${build_id}.txt.
37
18
  */
38
19
  logsBucket?: string;
39
20
  /**
40
- * Tags for annotation of a `Build`. These are not docker tags.
21
+ * Tags for organizing and filtering builds.
41
22
  */
42
23
  tags?: string[];
43
24
  /**
44
- * Substitutions data for `Build` resource.
25
+ * Substitutions data for Build resource.
45
26
  */
46
27
  substitutions?: {
47
- [k: string]: string;
28
+ [k: string]: string | undefined;
48
29
  };
49
30
  /**
50
- * A list of images to be pushed upon the successful completion of all build
51
- * steps.
52
- *
53
- * The images are pushed using the builder service account's credentials.
54
- *
55
- * The digests of the pushed images will be stored in the `Build` resource's
56
- * results field.
57
- *
58
- * If any of the images fail to be pushed, the build status is marked
59
- * `FAILURE`.
31
+ * A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.
60
32
  */
61
33
  images?: string[];
62
34
  options?: BuildOptions;
63
- source?: Source;
64
35
  artifacts?: Artifacts;
65
36
  /**
66
- * Amount of time that this build should be allowed to run, to second
67
- * granularity. If this amount of time elapses, work on the build will cease
68
- * and the build status will be `TIMEOUT`.
69
- *
70
- * Default time is ten minutes.
37
+ * Amount of time that this build should be allowed to run, to second granularity. If this amount of time elapses, work on the build will cease and the build status will be TIMEOUT.
71
38
  */
72
39
  timeout?: string;
73
40
  /**
74
41
  * Secrets to decrypt using Cloud Key Management Service.
75
42
  */
76
43
  secrets?: Secret[];
77
- [k: string]: unknown;
44
+ /**
45
+ * Use this field to specify the IAM service account to use at build time.
46
+ */
47
+ serviceAccount?: string;
48
+ /**
49
+ * Specifies the amount of time a build can be queued. If a build is in the queue for longer than the value set in queueTtl, the build expires and the build status is set to EXPIRED.
50
+ */
51
+ queueTtl?: string;
52
+ [k: string]: unknown | undefined;
78
53
  }
79
54
  /**
80
55
  * A step in the build pipeline.
81
56
  */
82
57
  export interface BuildStep {
83
58
  /**
84
- * Required. The name of the container image that will run this particular
85
- * build step.
86
- *
87
- * If the image is available in the host's Docker daemon's cache, it
88
- * will be run directly. If not, the host will attempt to pull the image
89
- * first, using the builder service account's credentials if necessary.
59
+ * Required. The name of the container image that will run this particular build step. If the image is available in the host's Docker daemon's cache, it will be run directly. If not, the host will attempt to pull the image first, using the builder service account's credentials if necessary.
90
60
  *
91
- * The Docker daemon's cache will already have the latest versions of all of
92
- * the officially supported build steps
93
- * ([https://github.com/GoogleCloudPlatform/cloud-builders](https://github.com/GoogleCloudPlatform/cloud-builders)).
94
- * The Docker daemon will also have cached many of the layers for some popular
95
- * images, like "ubuntu", "debian", but they will be refreshed at the time you
96
- * attempt to use them.
61
+ * The Docker daemon's cache will already have the latest versions of all of the officially supported build steps. The Docker daemon will also have cached many of the layers for some popular images, like "ubuntu", "debian", but they will be refreshed at the time you attempt to use them.
97
62
  *
98
- * If you built an image in a previous build step, it will be stored in the
99
- * host's Docker daemon's cache and is available to use as the name for a
100
- * later build step.
63
+ * If you built an image in a previous build step, it will be stored in the host's Docker daemon's cache and is available to use as the name for a later build step.
101
64
  */
102
65
  name?: string;
103
66
  /**
104
- * The ID(s) of the step(s) that this build step depends on.
105
- * This build step will not start until all the build steps in `wait_for`
106
- * have completed successfully. If `wait_for` is empty, this build step will
107
- * start when all previous build steps in the `Build.Steps` list have
108
- * completed successfully.
67
+ * In a build step, if you set the value of the allowFailure field to true, and the build step fails, then the build succeeds as long as all other build steps in that build succeed.
68
+ */
69
+ allowFailure?: boolean;
70
+ /**
71
+ * Specify that a build step failure can be ignored when that step returns a particular exit code.
72
+ */
73
+ allowExitCodes?: number[];
74
+ automapSubstitutions?: AutomapSubstitutions;
75
+ /**
76
+ * The ID(s) of the step(s) that this build step depends on. This build step will not start until all the build steps in waitFor have completed successfully. If waitFor is empty, this build step will start when all previous build steps in the list have completed successfully. If waitFor is set to '-', the step runs immediately when the build starts.
109
77
  */
110
78
  waitFor?: string[];
111
79
  /**
112
- * A list of environment variable definitions to be used when running a step.
113
- *
114
- * The elements are of the form "KEY=VALUE" for the environment variable "KEY"
115
- * being given the value "VALUE".
80
+ * A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".
116
81
  */
117
82
  env?: string[];
118
83
  /**
119
- * Entrypoint to be used instead of the build step image's default entrypoint.
120
- * If unset, the image's default entrypoint is used.
84
+ * Entrypoint to be used instead of the build step image's default entrypoint. If unset, the image's default entrypoint is used.
121
85
  */
122
86
  entrypoint?: string;
123
87
  /**
124
- * List of volumes to mount into the build step.
125
- *
126
- * Each volume is created as an empty volume prior to execution of the
127
- * build step. Upon completion of the build, volumes and their contents are
128
- * discarded.
129
- *
130
- * Using a named volume in only one step is not valid as it is indicative
131
- * of a build request with an incorrect configuration.
88
+ * Specify a shell script to execute in the step. If you specify script in a build step, you cannot specify args or entrypoint in the same step.
89
+ */
90
+ script?: string;
91
+ /**
92
+ * List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration.
132
93
  */
133
94
  volumes?: Volume[];
134
95
  /**
135
96
  * A list of arguments that will be presented to the step when it is started.
136
97
  *
137
- * If the image used to run the step's container has an entrypoint, the `args`
138
- * are used as arguments to that entrypoint. If the image does not define
139
- * an entrypoint, the first element in args is used as the entrypoint,
140
- * and the remainder will be used as arguments.
98
+ * If the image used to run the step's container has an entrypoint, the args are used as arguments to that entrypoint. If the image does not define an entrypoint, the first element in args is used as the entrypoint, and the remainder will be used as arguments.
141
99
  */
142
100
  args?: string[];
143
101
  /**
144
- * Time limit for executing this build step. If not defined, the step has no
145
- * time limit and will be allowed to continue to run until either it completes
146
- * or the build itself times out.
102
+ * Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
147
103
  */
148
104
  timeout?: string;
149
105
  /**
150
- * Unique identifier for this build step, used in `wait_for` to
151
- * reference this build step as a dependency.
106
+ * Unique identifier for this build step, used in waitFor to reference this build step as a dependency.
152
107
  */
153
108
  id?: string;
154
109
  /**
155
- * A list of environment variables which are encrypted using a Cloud Key
156
- * Management Service crypto key. These values must be specified in the
157
- * build's `Secret`.
110
+ * A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.
158
111
  */
159
112
  secretEnv?: string[];
160
113
  /**
161
114
  * Working directory to use when running this step's container.
162
115
  *
163
- * If this value is a relative path, it is relative to the build's working
164
- * directory. If this value is absolute, it may be outside the build's working
165
- * directory, in which case the contents of the path may not be persisted
166
- * across build step executions, unless a `volume` for that path is specified.
167
- *
168
- * If the build specifies a `RepoSource` with `dir` and a step with a `dir`,
169
- * which specifies an absolute path, the `RepoSource` `dir` is ignored for
170
- * the step's execution.
116
+ * If this value is a relative path, it is relative to the build's working directory. If this value is absolute, it may be outside the build's working directory, in which case the contents of the path may not be persisted across build step executions, unless a volume for that path is specified. If the build specifies a RepoSource with dir and a step with a dir, which specifies an absolute path, the RepoSource dir is ignored for the step's execution.
171
117
  */
172
118
  dir?: string;
173
- [k: string]: unknown;
174
119
  }
175
120
  /**
176
- * Volume describes a Docker container volume which is mounted into build steps
177
- * in order to persist files across build step execution.
121
+ * Volume describes a Docker container volume which is mounted into build steps in order to persist files across build step execution.
178
122
  */
179
123
  export interface Volume {
180
124
  /**
181
- * Name of the volume to mount.
182
- *
183
- * Volume names must be unique per build step and must be valid names for
184
- * Docker volumes. Each named volume must be used by at least two build steps.
125
+ * Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
185
126
  */
186
127
  name?: string;
187
128
  /**
188
- * Path at which to mount the volume.
189
- *
190
- * Paths must be absolute and cannot conflict with other volume paths on the
191
- * same build step or with certain reserved volume paths.
129
+ * Path at which to mount the volume. Paths must be absolute and cannot conflict with other volume paths on the same build step or with certain reserved volume paths.
192
130
  */
193
131
  path?: string;
194
- [k: string]: unknown;
132
+ [k: string]: unknown | undefined;
195
133
  }
196
134
  /**
197
135
  * Special options for this build.
198
136
  */
199
137
  export interface BuildOptions {
138
+ automapSubstitutions?: AutomapSubstitutions;
200
139
  /**
201
140
  * Compute Engine machine type on which to run the build.
202
141
  */
203
- machineType?:
204
- | "E2_HIGHCPU_2"
205
- | "E2_HIGHCPU_4"
206
- | "E2_HIGHCPU_8"
207
- | "E2_HIGHCPU_16"
208
- | "E2_HIGHCPU_32"
209
- | "E2_HIGHMEM_2"
210
- | "E2_HIGHMEM_4"
211
- | "E2_HIGHMEM_8"
212
- | "E2_HIGHMEM_16"
213
- | "E2_MEDIUM"
214
- | "E2_STANDARD_2"
215
- | "E2_STANDARD_4"
216
- | "E2_STANDARD_8"
217
- | "E2_STANDARD_16"
218
- | "E2_STANDARD_32"
219
- | "N1_HIGHCPU_8"
220
- | "N1_HIGHCPU_32"
221
- | "UNSPECIFIED";
222
- /**
223
- * Global list of volumes to mount for ALL build steps
224
- *
225
- * Each volume is created as an empty volume prior to starting the build
226
- * process. Upon completion of the build, volumes and their contents are
227
- * discarded. Global volume names and paths cannot conflict with the volumes
228
- * defined a build step.
229
- *
230
- * Using a global volume in a build with only one step is not valid as
231
- * it is indicative of a build request with an incorrect configuration.
142
+ machineType?: 'E2_HIGHCPU_8' | 'E2_HIGHCPU_32' | 'E2_MEDIUM' | 'N1_HIGHCPU_8' | 'N1_HIGHCPU_32' | 'UNSPECIFIED';
143
+ /**
144
+ * Global list of volumes to mount for ALL build steps. Each volume is created as an empty volume prior to starting the build process. Upon completion of the build, volumes and their contents are discarded. Global volume names and paths cannot conflict with the volumes defined a build step. Using a global volume in a build with only one step is not valid as it is indicative of a build request with an incorrect configuration.
232
145
  */
233
146
  volumes?: Volume[];
234
147
  /**
235
- * Option to define build log streaming behavior to Google Cloud
236
- * Storage.
148
+ * Option to define build log streaming behavior to Google Cloud Storage.
237
149
  */
238
- logStreamingOption?: "STREAM_DEFAULT" | "STREAM_ON" | "STREAM_OFF";
150
+ logStreamingOption?: 'STREAM_DEFAULT' | 'STREAM_ON' | 'STREAM_OFF';
239
151
  /**
240
- * Option to specify a `WorkerPool` for the build. User specifies the pool
241
- * with the format "[WORKERPOOL_PROJECT_ID]/[WORKERPOOL_NAME]".
242
- * This is an experimental field.
152
+ * Set the value of this field to the resource name of the private pool to run the build.
243
153
  */
244
- workerPool?: string;
154
+ pool?: {
155
+ /**
156
+ * Required. The full resource name of the private pool of the form 'projects/$PRIVATEPOOL_PROJECT_ID/locations/$REGION/workerPools/$PRIVATEPOOL_ID'.
157
+ */
158
+ name: string;
159
+ };
245
160
  /**
246
- * A list of global environment variable definitions that will exist for all
247
- * build steps in this build. If a variable is defined in both globally and in
248
- * a build step, the variable will use the build step value.
161
+ * A list of global environment variable definitions that will exist for all build steps in this build.
249
162
  *
250
- * The elements are of the form "KEY=VALUE" for the environment variable "KEY"
251
- * being given the value "VALUE".
163
+ * If a variable is defined both globally and in a build step, the variable will use the build step value. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".
252
164
  */
253
165
  env?: string[];
254
166
  /**
255
- * Option to specify the logging mode, which determines where the logs are
256
- * stored.
167
+ * Option to specify the logging mode, which determines where the logs are stored.
168
+ */
169
+ logging?: 'LOGGING_UNSPECIFIED' | 'LEGACY' | 'GCS_ONLY' | 'CLOUD_LOGGING_ONLY' | 'NONE';
170
+ /**
171
+ * Configure Cloud Build to create a default logs bucket within your own project in the same region as your build.
257
172
  */
258
- logging?: "LOGGING_UNSPECIFIED" | "LEGACY" | "GCS_ONLY" | "CLOUD_LOGGING_ONLY" | "NONE";
173
+ defaultLogsBucketBehavior?: 'DEFAULT_LOGS_BUCKET_BEHAVIOR_UNSPECIFIED' | 'REGIONAL_USER_OWNED_BUCKET';
259
174
  /**
260
175
  * Requested verifiability options.
261
176
  */
262
- requestedVerifyOption?: "NOT_VERIFIED" | "VERIFIED";
177
+ requestedVerifyOption?: 'NOT_VERIFIED' | 'VERIFIED';
263
178
  /**
264
- * Option to specify behavior when there is an error in the substitution
265
- * checks.
179
+ * Option to specify behavior when there is an error in the substitution checks.
266
180
  */
267
- substitutionOption?: "MUST_MATCH" | "ALLOW_LOOSE";
181
+ substitutionOption?: 'MUST_MATCH' | 'ALLOW_LOOSE';
268
182
  /**
269
- * Requested disk size for the VM that runs the build. Note that this is *NOT*
270
- * "disk free"; some of the space will be used by the operating system and
271
- * build utilities. Also note that this is the minimum disk size that will be
272
- * allocated for the build -- the build may run with a larger disk than
273
- * requested. At present, the maximum disk size is 1000GB; builds that request
274
- * more than the maximum are rejected with an error.
183
+ * Use this option to explicitly enable or disable bash parameter expansion in substitutions.
184
+ *
185
+ * If your build is invoked by a trigger, the dynamicSubstitutions field is always set to true and does not need to be specified in your build config file. If your build is invoked manually, you must set the dynamicSubstitutions field to true for bash parameter expansions to be interpreted when running your build.
275
186
  */
276
- diskSizeGb?: string;
187
+ dynamicSubstitutions?: boolean;
277
188
  /**
278
- * A list of global environment variables, which are encrypted using a Cloud
279
- * Key Management Service crypto key. These values must be specified in the
280
- * build's `Secret`. These variables will be available to all build steps
281
- * in this build.
189
+ * Requested disk size for the VM that runs the build.
190
+ *
191
+ * Note that this is *NOT* "disk free"; some of the space will be used by the operating system and build utilities. Also note that this is the minimum disk size that will be allocated for the build -- the build may run with a larger disk than requested. At present, the maximum disk size is 2000GB; builds that request more than the maximum are rejected with an error.
192
+ */
193
+ diskSizeGb?: number | string;
194
+ /**
195
+ * A list of global environment variables, which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret. These variables will be available to all build steps in this build.
282
196
  */
283
197
  secretEnv?: string[];
284
198
  /**
285
199
  * Requested hash for SourceProvenance.
286
200
  */
287
- sourceProvenanceHash?: ("NONE" | "SHA256" | "MD5")[];
288
- [k: string]: unknown;
201
+ sourceProvenanceHash?: ('NONE' | 'SHA256' | 'MD5')[];
202
+ }
203
+ /**
204
+ * Artifacts produced by the build that should be uploaded upon successful completion of all build steps.
205
+ */
206
+ export interface Artifacts {
207
+ objects?: ArtifactObjects;
208
+ /**
209
+ * Allows you to upload non-container Go modules to Go repositories in Artifact Registry.
210
+ */
211
+ goModules?: GoModules[];
212
+ /**
213
+ * Allows you to upload non-container Java artifacts to Maven repositories in Artifact Registry.
214
+ */
215
+ mavenArtifacts?: MavenArtifacts[];
216
+ /**
217
+ * Allows you to upload Python packages to Artifact Registry.
218
+ */
219
+ pythonPackages?: PythonPackages[];
220
+ /**
221
+ * Uploads your built NPM packages to supported repositories.
222
+ */
223
+ npmPackages?: NpmPackages[];
224
+ [k: string]: unknown | undefined;
289
225
  }
290
226
  /**
291
- * The location of the source files to build.
227
+ * A list of objects to be uploaded to Cloud Storage upon successful completion of all build steps. Files in the workspace matching specified paths globs will be uploaded to the specified Cloud Storage location using the builder service account's credentials. The location and generation of the uploaded objects will be stored in the Build resource's results field. If any objects fail to be pushed, the build is marked FAILURE.
292
228
  */
293
- export interface Source {
294
- storageSource?: StorageSource;
295
- repoSource?: RepoSource;
296
- [k: string]: unknown;
229
+ export interface ArtifactObjects {
230
+ /**
231
+ * Cloud Storage bucket and optional object path, in the form "gs://bucket/path/to/somewhere/". Files in the workspace matching any path pattern will be uploaded to Cloud Storage with this location as a prefix.
232
+ */
233
+ location?: string;
234
+ /**
235
+ * Path globs used to match files in the build's workspace.
236
+ */
237
+ paths?: string[];
238
+ [k: string]: unknown | undefined;
297
239
  }
298
240
  /**
299
- * If provided, get the source from this location in Google Cloud Storage.
241
+ * Allows you to upload non-container Go modules to Go repositories in Artifact Registry.
300
242
  */
301
- export interface StorageSource {
243
+ export interface GoModules {
302
244
  /**
303
- * Google Cloud Storage generation for the object. If the generation is
304
- * omitted, the latest generation will be used.
245
+ * The name of your Go repository in Artifact Registry.
305
246
  */
306
- generation?: string;
247
+ repositoryName: string;
307
248
  /**
308
- * Google Cloud Storage bucket containing the source (see
309
- * [Bucket Name
310
- * Requirements](https://cloud.google.com/storage/docs/bucket-naming#requirements)).
249
+ * The location for your repository in Artifact Registry.
311
250
  */
312
- bucket?: string;
251
+ repositoryLocation: string;
313
252
  /**
314
- * Google Cloud Storage object containing the source.
315
- *
316
- * This object must be a gzipped archive file (`.tar.gz`) containing source to
317
- * build.
253
+ * The ID of the Google Cloud project that contains your Artifact Registry Go repository.
318
254
  */
319
- object?: string;
320
- [k: string]: unknown;
255
+ repositoryProject_id: string;
256
+ /**
257
+ * The path to the go.mod file in the build's workspace.
258
+ */
259
+ sourcePath: string;
260
+ /**
261
+ * The local directory that contains the Go module to upload. It is recommended to use an absolute path for the value.
262
+ */
263
+ modulePath: string;
264
+ /**
265
+ * The version of the Go module.
266
+ */
267
+ moduleVersion: string;
321
268
  }
322
269
  /**
323
- * If provided, get the source from this location in a Cloud Source
324
- * Repository.
270
+ * Allows you to upload non-container Java artifacts to Maven repositories in Artifact Registry.
325
271
  */
326
- export interface RepoSource {
272
+ export interface MavenArtifacts {
327
273
  /**
328
- * Name of the tag to build.
274
+ * Required. Name of the Artifact Registry repository to store Java artifacts.
329
275
  */
330
- tagName?: string;
276
+ repository: string;
331
277
  /**
332
- * ID of the project that owns the Cloud Source Repository. If omitted, the
333
- * project ID requesting the build is assumed.
278
+ * Required. The application file path.
334
279
  */
335
- projectId?: string;
280
+ path: string;
336
281
  /**
337
- * Name of the Cloud Source Repository. If omitted, the name "default" is
338
- * assumed.
282
+ * Required. Name of your package file created from your build step
339
283
  */
340
- repoName?: string;
284
+ artifactId: string;
341
285
  /**
342
- * Explicit commit SHA to build.
286
+ * Required. Uniquely identifies your project across all Maven projects, in the format com.mycompany.app.
343
287
  */
344
- commitSha?: string;
345
- /**
346
- * Directory, relative to the source root, in which to run the build.
347
- *
348
- * This must be a relative path. If a step's `dir` is specified and is an
349
- * absolute path, this value is ignored for that step's execution.
350
- */
351
- dir?: string;
288
+ groupId: string;
352
289
  /**
353
- * Name of the branch to build.
290
+ * Required. The version number for your application.
354
291
  */
355
- branchName?: string;
356
- [k: string]: unknown;
292
+ version: string;
357
293
  }
358
294
  /**
359
- * Artifacts produced by the build that should be uploaded upon
360
- * successful completion of all build steps.
295
+ * Allows you to upload Python packages to Artifact Registry.
361
296
  */
362
- export interface Artifacts {
363
- objects?: ArtifactObjects;
297
+ export interface PythonPackages {
364
298
  /**
365
- * A list of images to be pushed upon the successful completion of all build
366
- * steps.
367
- *
368
- * The images will be pushed using the builder service account's credentials.
369
- *
370
- * The digests of the pushed images will be stored in the Build resource's
371
- * results field.
372
- *
373
- * If any of the images fail to be pushed, the build is marked FAILURE.
299
+ * Required. Name of the Artifact Registry repository to store the Python package.
374
300
  */
375
- images?: string[];
376
- [k: string]: unknown;
301
+ repository: string;
302
+ /**
303
+ * Required. The package file paths.
304
+ */
305
+ paths: string[];
377
306
  }
378
307
  /**
379
- * A list of objects to be uploaded to Cloud Storage upon successful
380
- * completion of all build steps.
381
- *
382
- * Files in the workspace matching specified paths globs will be uploaded to
383
- * the specified Cloud Storage location using the builder service account's
384
- * credentials.
385
- *
386
- * The location and generation of the uploaded objects will be stored in the
387
- * Build resource's results field.
388
- *
389
- * If any objects fail to be pushed, the build is marked FAILURE.
308
+ * Uploads your built NPM packages to supported repositories.
390
309
  */
391
- export interface ArtifactObjects {
310
+ export interface NpmPackages {
392
311
  /**
393
- * Cloud Storage bucket and optional object path, in the form
394
- * "gs://bucket/path/to/somewhere/". (see [Bucket Name
395
- * Requirements](https://cloud.google.com/storage/docs/bucket-naming#requirements)).
396
- *
397
- * Files in the workspace matching any path pattern will be uploaded to
398
- * Cloud Storage with this location as a prefix.
312
+ * Required. Name of the Artifact Registry repository to store the NPM package.
399
313
  */
400
- location?: string;
314
+ repository: string;
401
315
  /**
402
- * Path globs used to match files in the build's workspace.
316
+ * Required. The path for the local directory containing the NPM package that you want to upload to Artifact Registry. Google recommends using an absolute path. Your packagePath value can be . to use the current working directory, but the field cannot be omitted or left empty. This directory must contain a package.json file.
403
317
  */
404
- paths?: string[];
405
- [k: string]: unknown;
318
+ packagePath: string;
406
319
  }
407
320
  /**
408
- * Pairs a set of secret environment variables containing encrypted
409
- * values with the Cloud KMS key to use to decrypt the value.
321
+ * Pairs a set of secret environment variables containing encrypted values with the Cloud KMS key to use to decrypt the value.
410
322
  */
411
323
  export interface Secret {
412
324
  /**
@@ -414,15 +326,10 @@ export interface Secret {
414
326
  */
415
327
  kmsKeyName?: string;
416
328
  /**
417
- * Map of environment variable name to its encrypted value.
418
- *
419
- * Secret environment variables must be unique across all of a build's
420
- * secrets, and must be used by at least one build step. Values can be at most
421
- * 64 KB in size. There can be at most 100 secret values across all of a
422
- * build's secrets.
329
+ * Map of environment variable name to its encrypted value. Secret environment variables must be unique across all of a build's secrets, and must be used by at least one build step. Values can be at most 64 KB in size. There can be at most 100 secret values across all of a build's secrets.
423
330
  */
424
331
  secretEnv?: {
425
- [k: string]: string;
332
+ [k: string]: string | undefined;
426
333
  };
427
- [k: string]: unknown;
334
+ [k: string]: unknown | undefined;
428
335
  }
package/package.json CHANGED
@@ -1,14 +1,9 @@
1
1
  {
2
2
  "author": "Florian Imdahl <git@ffflorian.de>",
3
- "dependencies": {},
4
3
  "description": "TypeScript definitions for cloudbuild.",
5
- "license": "MIT",
6
- "main": "index.d.ts",
4
+ "license": "GPL-3.0",
7
5
  "name": "@schemastore/cloudbuild",
8
- "repository": "https://github.com/ffflorian/schemastore-updater/tree/main/schemas/cloudbuild",
9
- "scripts": {},
10
- "typesPublisherContentHash": "778f15989f2ad6fddffdd9d41c6a8b3fd071ee4f5c15fbddd99f02f7a6d1f29a",
6
+ "private": false,
11
7
  "types": "index.d.ts",
12
- "version": "0.0.7",
13
- "typeScriptVersion": "2.2"
8
+ "version": "1.0.0"
14
9
  }