You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy/helm/nifi-operator/crds/crds.yaml
+96Lines changed: 96 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -602,6 +602,8 @@ spec:
602
602
capacity: null
603
603
databaseRepo:
604
604
capacity: null
605
+
fileBasedRepo:
606
+
capacity: null
605
607
flowfileRepo:
606
608
capacity: null
607
609
provenanceRepo:
@@ -745,6 +747,52 @@ spec:
745
747
nullable: true
746
748
type: string
747
749
type: object
750
+
fileBasedRepo:
751
+
default:
752
+
capacity: null
753
+
description: |-
754
+
Used as persistance for file-based authorization.
755
+
Default size: 16MB
756
+
properties:
757
+
capacity:
758
+
description: "Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.\n\nThe serialization format is:\n\n``` <quantity> ::= <signedNumber><suffix>\n\n\t(Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)\n\n<digit> ::= 0 | 1 | ... | 9 <digits> ::= <digit> | <digit><digits> <number> ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign> ::= \"+\" | \"-\" <signedNumber> ::= <number> | <sign><number> <suffix> ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI> ::= Ki | Mi | Gi | Ti | Pi | Ei\n\n\t(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)\n\n<decimalSI> ::= m | \"\" | k | M | G | T | P | E\n\n\t(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)\n\n<decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```\n\nNo matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.\n\nWhen a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.\n\nBefore serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:\n\n- No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.\n\nThe sign will be omitted unless the number is negative.\n\nExamples:\n\n- 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"\n\nNote that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.\n\nNon-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)\n\nThis format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation."
759
+
nullable: true
760
+
type: string
761
+
selectors:
762
+
description: A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
763
+
nullable: true
764
+
properties:
765
+
matchExpressions:
766
+
description: matchExpressions is a list of label selector requirements. The requirements are ANDed.
767
+
items:
768
+
description: A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
769
+
properties:
770
+
key:
771
+
description: key is the label key that the selector applies to.
772
+
type: string
773
+
operator:
774
+
description: operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
775
+
type: string
776
+
values:
777
+
description: values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
778
+
items:
779
+
type: string
780
+
type: array
781
+
required:
782
+
- key
783
+
- operator
784
+
type: object
785
+
type: array
786
+
matchLabels:
787
+
additionalProperties:
788
+
type: string
789
+
description: matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed.
790
+
type: object
791
+
type: object
792
+
storageClass:
793
+
nullable: true
794
+
type: string
795
+
type: object
748
796
flowfileRepo:
749
797
default:
750
798
capacity: null
@@ -1154,6 +1202,8 @@ spec:
1154
1202
capacity: null
1155
1203
databaseRepo:
1156
1204
capacity: null
1205
+
fileBasedRepo:
1206
+
capacity: null
1157
1207
flowfileRepo:
1158
1208
capacity: null
1159
1209
provenanceRepo:
@@ -1297,6 +1347,52 @@ spec:
1297
1347
nullable: true
1298
1348
type: string
1299
1349
type: object
1350
+
fileBasedRepo:
1351
+
default:
1352
+
capacity: null
1353
+
description: |-
1354
+
Used as persistance for file-based authorization.
1355
+
Default size: 16MB
1356
+
properties:
1357
+
capacity:
1358
+
description: "Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.\n\nThe serialization format is:\n\n``` <quantity> ::= <signedNumber><suffix>\n\n\t(Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)\n\n<digit> ::= 0 | 1 | ... | 9 <digits> ::= <digit> | <digit><digits> <number> ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign> ::= \"+\" | \"-\" <signedNumber> ::= <number> | <sign><number> <suffix> ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI> ::= Ki | Mi | Gi | Ti | Pi | Ei\n\n\t(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)\n\n<decimalSI> ::= m | \"\" | k | M | G | T | P | E\n\n\t(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)\n\n<decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```\n\nNo matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.\n\nWhen a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.\n\nBefore serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:\n\n- No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.\n\nThe sign will be omitted unless the number is negative.\n\nExamples:\n\n- 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"\n\nNote that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.\n\nNon-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)\n\nThis format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation."
1359
+
nullable: true
1360
+
type: string
1361
+
selectors:
1362
+
description: A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
1363
+
nullable: true
1364
+
properties:
1365
+
matchExpressions:
1366
+
description: matchExpressions is a list of label selector requirements. The requirements are ANDed.
1367
+
items:
1368
+
description: A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
1369
+
properties:
1370
+
key:
1371
+
description: key is the label key that the selector applies to.
1372
+
type: string
1373
+
operator:
1374
+
description: operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
1375
+
type: string
1376
+
values:
1377
+
description: values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
1378
+
items:
1379
+
type: string
1380
+
type: array
1381
+
required:
1382
+
- key
1383
+
- operator
1384
+
type: object
1385
+
type: array
1386
+
matchLabels:
1387
+
additionalProperties:
1388
+
type: string
1389
+
description: matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed.
0 commit comments