generators.external-secrets.io_vaultdynamicsecrets.yaml 40 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720
  1. apiVersion: apiextensions.k8s.io/v1
  2. kind: CustomResourceDefinition
  3. metadata:
  4. annotations:
  5. controller-gen.kubebuilder.io/version: v0.16.2
  6. labels:
  7. external-secrets.io/component: controller
  8. name: vaultdynamicsecrets.generators.external-secrets.io
  9. spec:
  10. group: generators.external-secrets.io
  11. names:
  12. categories:
  13. - vaultdynamicsecret
  14. kind: VaultDynamicSecret
  15. listKind: VaultDynamicSecretList
  16. plural: vaultdynamicsecrets
  17. shortNames:
  18. - vaultdynamicsecret
  19. singular: vaultdynamicsecret
  20. scope: Namespaced
  21. versions:
  22. - name: v1alpha1
  23. schema:
  24. openAPIV3Schema:
  25. properties:
  26. apiVersion:
  27. description: |-
  28. APIVersion defines the versioned schema of this representation of an object.
  29. Servers should convert recognized schemas to the latest internal value, and
  30. may reject unrecognized values.
  31. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
  32. type: string
  33. kind:
  34. description: |-
  35. Kind is a string value representing the REST resource this object represents.
  36. Servers may infer this from the endpoint the client submits requests to.
  37. Cannot be updated.
  38. In CamelCase.
  39. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
  40. type: string
  41. metadata:
  42. type: object
  43. spec:
  44. properties:
  45. controller:
  46. description: |-
  47. Used to select the correct ESO controller (think: ingress.ingressClassName)
  48. The ESO controller is instantiated with a specific controller name and filters VDS based on this property
  49. type: string
  50. method:
  51. description: Vault API method to use (GET/POST/other)
  52. type: string
  53. parameters:
  54. description: Parameters to pass to Vault write (for non-GET methods)
  55. x-kubernetes-preserve-unknown-fields: true
  56. path:
  57. description: Vault path to obtain the dynamic secret from
  58. type: string
  59. provider:
  60. description: Vault provider common spec
  61. properties:
  62. auth:
  63. description: Auth configures how secret-manager authenticates
  64. with the Vault server.
  65. properties:
  66. appRole:
  67. description: |-
  68. AppRole authenticates with Vault using the App Role auth mechanism,
  69. with the role and secret stored in a Kubernetes Secret resource.
  70. properties:
  71. path:
  72. default: approle
  73. description: |-
  74. Path where the App Role authentication backend is mounted
  75. in Vault, e.g: "approle"
  76. type: string
  77. roleId:
  78. description: |-
  79. RoleID configured in the App Role authentication backend when setting
  80. up the authentication backend in Vault.
  81. type: string
  82. roleRef:
  83. description: |-
  84. Reference to a key in a Secret that contains the App Role ID used
  85. to authenticate with Vault.
  86. The `key` field must be specified and denotes which entry within the Secret
  87. resource is used as the app role id.
  88. properties:
  89. key:
  90. description: |-
  91. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  92. defaulted, in others it may be required.
  93. type: string
  94. name:
  95. description: The name of the Secret resource being
  96. referred to.
  97. type: string
  98. namespace:
  99. description: |-
  100. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  101. to the namespace of the referent.
  102. type: string
  103. type: object
  104. secretRef:
  105. description: |-
  106. Reference to a key in a Secret that contains the App Role secret used
  107. to authenticate with Vault.
  108. The `key` field must be specified and denotes which entry within the Secret
  109. resource is used as the app role secret.
  110. properties:
  111. key:
  112. description: |-
  113. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  114. defaulted, in others it may be required.
  115. type: string
  116. name:
  117. description: The name of the Secret resource being
  118. referred to.
  119. type: string
  120. namespace:
  121. description: |-
  122. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  123. to the namespace of the referent.
  124. type: string
  125. type: object
  126. required:
  127. - path
  128. - secretRef
  129. type: object
  130. cert:
  131. description: |-
  132. Cert authenticates with TLS Certificates by passing client certificate, private key and ca certificate
  133. Cert authentication method
  134. properties:
  135. clientCert:
  136. description: |-
  137. ClientCert is a certificate to authenticate using the Cert Vault
  138. authentication method
  139. properties:
  140. key:
  141. description: |-
  142. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  143. defaulted, in others it may be required.
  144. type: string
  145. name:
  146. description: The name of the Secret resource being
  147. referred to.
  148. type: string
  149. namespace:
  150. description: |-
  151. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  152. to the namespace of the referent.
  153. type: string
  154. type: object
  155. secretRef:
  156. description: |-
  157. SecretRef to a key in a Secret resource containing client private key to
  158. authenticate with Vault using the Cert authentication method
  159. properties:
  160. key:
  161. description: |-
  162. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  163. defaulted, in others it may be required.
  164. type: string
  165. name:
  166. description: The name of the Secret resource being
  167. referred to.
  168. type: string
  169. namespace:
  170. description: |-
  171. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  172. to the namespace of the referent.
  173. type: string
  174. type: object
  175. type: object
  176. iam:
  177. description: |-
  178. Iam authenticates with vault by passing a special AWS request signed with AWS IAM credentials
  179. AWS IAM authentication method
  180. properties:
  181. externalID:
  182. description: AWS External ID set on assumed IAM roles
  183. type: string
  184. jwt:
  185. description: Specify a service account with IRSA enabled
  186. properties:
  187. serviceAccountRef:
  188. description: A reference to a ServiceAccount resource.
  189. properties:
  190. audiences:
  191. description: |-
  192. Audience specifies the `aud` claim for the service account token
  193. If the service account uses a well-known annotation for e.g. IRSA or GCP Workload Identity
  194. then this audiences will be appended to the list
  195. items:
  196. type: string
  197. type: array
  198. name:
  199. description: The name of the ServiceAccount resource
  200. being referred to.
  201. type: string
  202. namespace:
  203. description: |-
  204. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  205. to the namespace of the referent.
  206. type: string
  207. required:
  208. - name
  209. type: object
  210. type: object
  211. path:
  212. description: 'Path where the AWS auth method is enabled
  213. in Vault, e.g: "aws"'
  214. type: string
  215. region:
  216. description: AWS region
  217. type: string
  218. role:
  219. description: This is the AWS role to be assumed before
  220. talking to vault
  221. type: string
  222. secretRef:
  223. description: Specify credentials in a Secret object
  224. properties:
  225. accessKeyIDSecretRef:
  226. description: The AccessKeyID is used for authentication
  227. properties:
  228. key:
  229. description: |-
  230. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  231. defaulted, in others it may be required.
  232. type: string
  233. name:
  234. description: The name of the Secret resource being
  235. referred to.
  236. type: string
  237. namespace:
  238. description: |-
  239. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  240. to the namespace of the referent.
  241. type: string
  242. type: object
  243. secretAccessKeySecretRef:
  244. description: The SecretAccessKey is used for authentication
  245. properties:
  246. key:
  247. description: |-
  248. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  249. defaulted, in others it may be required.
  250. type: string
  251. name:
  252. description: The name of the Secret resource being
  253. referred to.
  254. type: string
  255. namespace:
  256. description: |-
  257. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  258. to the namespace of the referent.
  259. type: string
  260. type: object
  261. sessionTokenSecretRef:
  262. description: |-
  263. The SessionToken used for authentication
  264. This must be defined if AccessKeyID and SecretAccessKey are temporary credentials
  265. see: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html
  266. properties:
  267. key:
  268. description: |-
  269. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  270. defaulted, in others it may be required.
  271. type: string
  272. name:
  273. description: The name of the Secret resource being
  274. referred to.
  275. type: string
  276. namespace:
  277. description: |-
  278. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  279. to the namespace of the referent.
  280. type: string
  281. type: object
  282. type: object
  283. vaultAwsIamServerID:
  284. description: 'X-Vault-AWS-IAM-Server-ID is an additional
  285. header used by Vault IAM auth method to mitigate against
  286. different types of replay attacks. More details here:
  287. https://developer.hashicorp.com/vault/docs/auth/aws'
  288. type: string
  289. vaultRole:
  290. description: Vault Role. In vault, a role describes an
  291. identity with a set of permissions, groups, or policies
  292. you want to attach a user of the secrets engine
  293. type: string
  294. required:
  295. - vaultRole
  296. type: object
  297. jwt:
  298. description: |-
  299. Jwt authenticates with Vault by passing role and JWT token using the
  300. JWT/OIDC authentication method
  301. properties:
  302. kubernetesServiceAccountToken:
  303. description: |-
  304. Optional ServiceAccountToken specifies the Kubernetes service account for which to request
  305. a token for with the `TokenRequest` API.
  306. properties:
  307. audiences:
  308. description: |-
  309. Optional audiences field that will be used to request a temporary Kubernetes service
  310. account token for the service account referenced by `serviceAccountRef`.
  311. Defaults to a single audience `vault` it not specified.
  312. Deprecated: use serviceAccountRef.Audiences instead
  313. items:
  314. type: string
  315. type: array
  316. expirationSeconds:
  317. description: |-
  318. Optional expiration time in seconds that will be used to request a temporary
  319. Kubernetes service account token for the service account referenced by
  320. `serviceAccountRef`.
  321. Deprecated: this will be removed in the future.
  322. Defaults to 10 minutes.
  323. format: int64
  324. type: integer
  325. serviceAccountRef:
  326. description: Service account field containing the
  327. name of a kubernetes ServiceAccount.
  328. properties:
  329. audiences:
  330. description: |-
  331. Audience specifies the `aud` claim for the service account token
  332. If the service account uses a well-known annotation for e.g. IRSA or GCP Workload Identity
  333. then this audiences will be appended to the list
  334. items:
  335. type: string
  336. type: array
  337. name:
  338. description: The name of the ServiceAccount resource
  339. being referred to.
  340. type: string
  341. namespace:
  342. description: |-
  343. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  344. to the namespace of the referent.
  345. type: string
  346. required:
  347. - name
  348. type: object
  349. required:
  350. - serviceAccountRef
  351. type: object
  352. path:
  353. default: jwt
  354. description: |-
  355. Path where the JWT authentication backend is mounted
  356. in Vault, e.g: "jwt"
  357. type: string
  358. role:
  359. description: |-
  360. Role is a JWT role to authenticate using the JWT/OIDC Vault
  361. authentication method
  362. type: string
  363. secretRef:
  364. description: |-
  365. Optional SecretRef that refers to a key in a Secret resource containing JWT token to
  366. authenticate with Vault using the JWT/OIDC authentication method.
  367. properties:
  368. key:
  369. description: |-
  370. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  371. defaulted, in others it may be required.
  372. type: string
  373. name:
  374. description: The name of the Secret resource being
  375. referred to.
  376. type: string
  377. namespace:
  378. description: |-
  379. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  380. to the namespace of the referent.
  381. type: string
  382. type: object
  383. required:
  384. - path
  385. type: object
  386. kubernetes:
  387. description: |-
  388. Kubernetes authenticates with Vault by passing the ServiceAccount
  389. token stored in the named Secret resource to the Vault server.
  390. properties:
  391. mountPath:
  392. default: kubernetes
  393. description: |-
  394. Path where the Kubernetes authentication backend is mounted in Vault, e.g:
  395. "kubernetes"
  396. type: string
  397. role:
  398. description: |-
  399. A required field containing the Vault Role to assume. A Role binds a
  400. Kubernetes ServiceAccount with a set of Vault policies.
  401. type: string
  402. secretRef:
  403. description: |-
  404. Optional secret field containing a Kubernetes ServiceAccount JWT used
  405. for authenticating with Vault. If a name is specified without a key,
  406. `token` is the default. If one is not specified, the one bound to
  407. the controller will be used.
  408. properties:
  409. key:
  410. description: |-
  411. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  412. defaulted, in others it may be required.
  413. type: string
  414. name:
  415. description: The name of the Secret resource being
  416. referred to.
  417. type: string
  418. namespace:
  419. description: |-
  420. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  421. to the namespace of the referent.
  422. type: string
  423. type: object
  424. serviceAccountRef:
  425. description: |-
  426. Optional service account field containing the name of a kubernetes ServiceAccount.
  427. If the service account is specified, the service account secret token JWT will be used
  428. for authenticating with Vault. If the service account selector is not supplied,
  429. the secretRef will be used instead.
  430. properties:
  431. audiences:
  432. description: |-
  433. Audience specifies the `aud` claim for the service account token
  434. If the service account uses a well-known annotation for e.g. IRSA or GCP Workload Identity
  435. then this audiences will be appended to the list
  436. items:
  437. type: string
  438. type: array
  439. name:
  440. description: The name of the ServiceAccount resource
  441. being referred to.
  442. type: string
  443. namespace:
  444. description: |-
  445. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  446. to the namespace of the referent.
  447. type: string
  448. required:
  449. - name
  450. type: object
  451. required:
  452. - mountPath
  453. - role
  454. type: object
  455. ldap:
  456. description: |-
  457. Ldap authenticates with Vault by passing username/password pair using
  458. the LDAP authentication method
  459. properties:
  460. path:
  461. default: ldap
  462. description: |-
  463. Path where the LDAP authentication backend is mounted
  464. in Vault, e.g: "ldap"
  465. type: string
  466. secretRef:
  467. description: |-
  468. SecretRef to a key in a Secret resource containing password for the LDAP
  469. user used to authenticate with Vault using the LDAP authentication
  470. method
  471. properties:
  472. key:
  473. description: |-
  474. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  475. defaulted, in others it may be required.
  476. type: string
  477. name:
  478. description: The name of the Secret resource being
  479. referred to.
  480. type: string
  481. namespace:
  482. description: |-
  483. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  484. to the namespace of the referent.
  485. type: string
  486. type: object
  487. username:
  488. description: |-
  489. Username is a LDAP user name used to authenticate using the LDAP Vault
  490. authentication method
  491. type: string
  492. required:
  493. - path
  494. - username
  495. type: object
  496. namespace:
  497. description: |-
  498. Name of the vault namespace to authenticate to. This can be different than the namespace your secret is in.
  499. Namespaces is a set of features within Vault Enterprise that allows
  500. Vault environments to support Secure Multi-tenancy. e.g: "ns1".
  501. More about namespaces can be found here https://www.vaultproject.io/docs/enterprise/namespaces
  502. This will default to Vault.Namespace field if set, or empty otherwise
  503. type: string
  504. tokenSecretRef:
  505. description: TokenSecretRef authenticates with Vault by presenting
  506. a token.
  507. properties:
  508. key:
  509. description: |-
  510. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  511. defaulted, in others it may be required.
  512. type: string
  513. name:
  514. description: The name of the Secret resource being referred
  515. to.
  516. type: string
  517. namespace:
  518. description: |-
  519. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  520. to the namespace of the referent.
  521. type: string
  522. type: object
  523. userPass:
  524. description: UserPass authenticates with Vault by passing
  525. username/password pair
  526. properties:
  527. path:
  528. default: user
  529. description: |-
  530. Path where the UserPassword authentication backend is mounted
  531. in Vault, e.g: "user"
  532. type: string
  533. secretRef:
  534. description: |-
  535. SecretRef to a key in a Secret resource containing password for the
  536. user used to authenticate with Vault using the UserPass authentication
  537. method
  538. properties:
  539. key:
  540. description: |-
  541. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  542. defaulted, in others it may be required.
  543. type: string
  544. name:
  545. description: The name of the Secret resource being
  546. referred to.
  547. type: string
  548. namespace:
  549. description: |-
  550. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  551. to the namespace of the referent.
  552. type: string
  553. type: object
  554. username:
  555. description: |-
  556. Username is a user name used to authenticate using the UserPass Vault
  557. authentication method
  558. type: string
  559. required:
  560. - path
  561. - username
  562. type: object
  563. type: object
  564. caBundle:
  565. description: |-
  566. PEM encoded CA bundle used to validate Vault server certificate. Only used
  567. if the Server URL is using HTTPS protocol. This parameter is ignored for
  568. plain HTTP protocol connection. If not set the system root certificates
  569. are used to validate the TLS connection.
  570. format: byte
  571. type: string
  572. caProvider:
  573. description: The provider for the CA bundle to use to validate
  574. Vault server certificate.
  575. properties:
  576. key:
  577. description: The key where the CA certificate can be found
  578. in the Secret or ConfigMap.
  579. type: string
  580. name:
  581. description: The name of the object located at the provider
  582. type.
  583. type: string
  584. namespace:
  585. description: |-
  586. The namespace the Provider type is in.
  587. Can only be defined when used in a ClusterSecretStore.
  588. type: string
  589. type:
  590. description: The type of provider to use such as "Secret",
  591. or "ConfigMap".
  592. enum:
  593. - Secret
  594. - ConfigMap
  595. type: string
  596. required:
  597. - name
  598. - type
  599. type: object
  600. forwardInconsistent:
  601. description: |-
  602. ForwardInconsistent tells Vault to forward read-after-write requests to the Vault
  603. leader instead of simply retrying within a loop. This can increase performance if
  604. the option is enabled serverside.
  605. https://www.vaultproject.io/docs/configuration/replication#allow_forwarding_via_header
  606. type: boolean
  607. headers:
  608. additionalProperties:
  609. type: string
  610. description: Headers to be added in Vault request
  611. type: object
  612. namespace:
  613. description: |-
  614. Name of the vault namespace. Namespaces is a set of features within Vault Enterprise that allows
  615. Vault environments to support Secure Multi-tenancy. e.g: "ns1".
  616. More about namespaces can be found here https://www.vaultproject.io/docs/enterprise/namespaces
  617. type: string
  618. path:
  619. description: |-
  620. Path is the mount path of the Vault KV backend endpoint, e.g:
  621. "secret". The v2 KV secret engine version specific "/data" path suffix
  622. for fetching secrets from Vault is optional and will be appended
  623. if not present in specified path.
  624. type: string
  625. readYourWrites:
  626. description: |-
  627. ReadYourWrites ensures isolated read-after-write semantics by
  628. providing discovered cluster replication states in each request.
  629. More information about eventual consistency in Vault can be found here
  630. https://www.vaultproject.io/docs/enterprise/consistency
  631. type: boolean
  632. server:
  633. description: 'Server is the connection address for the Vault server,
  634. e.g: "https://vault.example.com:8200".'
  635. type: string
  636. tls:
  637. description: |-
  638. The configuration used for client side related TLS communication, when the Vault server
  639. requires mutual authentication. Only used if the Server URL is using HTTPS protocol.
  640. This parameter is ignored for plain HTTP protocol connection.
  641. It's worth noting this configuration is different from the "TLS certificates auth method",
  642. which is available under the `auth.cert` section.
  643. properties:
  644. certSecretRef:
  645. description: |-
  646. CertSecretRef is a certificate added to the transport layer
  647. when communicating with the Vault server.
  648. If no key for the Secret is specified, external-secret will default to 'tls.crt'.
  649. properties:
  650. key:
  651. description: |-
  652. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  653. defaulted, in others it may be required.
  654. type: string
  655. name:
  656. description: The name of the Secret resource being referred
  657. to.
  658. type: string
  659. namespace:
  660. description: |-
  661. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  662. to the namespace of the referent.
  663. type: string
  664. type: object
  665. keySecretRef:
  666. description: |-
  667. KeySecretRef to a key in a Secret resource containing client private key
  668. added to the transport layer when communicating with the Vault server.
  669. If no key for the Secret is specified, external-secret will default to 'tls.key'.
  670. properties:
  671. key:
  672. description: |-
  673. The key of the entry in the Secret resource's `data` field to be used. Some instances of this field may be
  674. defaulted, in others it may be required.
  675. type: string
  676. name:
  677. description: The name of the Secret resource being referred
  678. to.
  679. type: string
  680. namespace:
  681. description: |-
  682. Namespace of the resource being referred to. Ignored if referent is not cluster-scoped. cluster-scoped defaults
  683. to the namespace of the referent.
  684. type: string
  685. type: object
  686. type: object
  687. version:
  688. default: v2
  689. description: |-
  690. Version is the Vault KV secret engine version. This can be either "v1" or
  691. "v2". Version defaults to "v2".
  692. enum:
  693. - v1
  694. - v2
  695. type: string
  696. required:
  697. - auth
  698. - server
  699. type: object
  700. resultType:
  701. default: Data
  702. description: |-
  703. Result type defines which data is returned from the generator.
  704. By default it is the "data" section of the Vault API response.
  705. When using e.g. /auth/token/create the "data" section is empty but
  706. the "auth" section contains the generated token.
  707. Please refer to the vault docs regarding the result data structure.
  708. enum:
  709. - Data
  710. - Auth
  711. type: string
  712. required:
  713. - path
  714. - provider
  715. type: object
  716. type: object
  717. served: true
  718. storage: true
  719. subresources:
  720. status: {}