fix: update provider examples to use apiVersion external-secrets.io/v1 (#4757)

This PR updates all documentaion files where:
* `apiVersion: external-secrets.io/v1beta`

is replaced with:
* `apiVersion: external-secrets.io/v1`

Only applied for the following resource kind:
* SecretStore
* ClusterSecretStore
* ExternalSecret
* ClusterExternalSecret

This aligns the provider examples with the latest External Secrets
Operator API.

Signed-off-by: Rowan Ruseler <rowanruseler@gmail.com>
Signed-off-by: Rowan Ruseler <rowan@miro.com>
Signed-off-by: Gustavo Fernandes de Carvalho <17139678+gusfcarvalho@users.noreply.github.com>
Co-authored-by: Gustavo Fernandes de Carvalho <17139678+gusfcarvalho@users.noreply.github.com>

docs/api/externalsecret.md

@@ -25,7 +25,7 @@ With `refreshPolicy: CreatedOnce`, the controller will:
 
 Example:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example
@@ -44,7 +44,7 @@ With `refreshPolicy: Periodic` (the default behavior), the controller will:
 
 Example:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example
@@ -64,7 +64,7 @@ With `refreshPolicy: OnChange`, the controller will:
 
 Example:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example

docs/api/generator/ecr.md

@@ -28,4 +28,4 @@ You can choose from three authentication mechanisms:
 Example `ExternalSecret` that references the ECR generator:
 ```yaml
 {% include 'generator-ecr-example.yaml' %}
-```
+```

docs/api/generator/index.md

@@ -1,2 +1,2 @@
 
-Generators allow you to generate values. See [Generators Guide](../../guides/generator.md)
+Generators allow you to generate values. See [Generators Guide](../../guides/generator.md)

docs/contributing/roadmap.md

@@ -7,7 +7,7 @@ The following external-secret custom resource APIs are considered stable:
 * `SecretStore`
 * `ClusterSecretStore`
 
-These CRDs are currently at `v1beta1` and are considered production ready. Going forward, breaking changes to these APIs will be accompanied by a conversion mechanism.
+These CRDs are currently at `v1` and are considered production ready. Going forward, breaking changes to these APIs will be accompanied by a conversion mechanism.
 
 We have identified the following areas of work. This is subject to change while we gather feedback. We have a [GitHub Project Board](https://github.com/orgs/external-secrets/projects/2/views/1) where we organize issues and milestones on a high level.
 

docs/guides/common-k8s-secret-types.md

@@ -39,7 +39,7 @@ Alternately, if you only have the container registry name and password value, yo
 
 ```yaml
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: dk-cfg-example

docs/guides/decoding-strategy.md

@@ -47,4 +47,4 @@ data:
 At this time, decoding Strategy Auto is only trying to check if the original input is valid to perform Base64 operations. This means that some non-encoded secret values might end up being decoded, producing gibberish. This is the case for numbered values like `123456` or some specially crafted string values such as `happy/street`. 
 
 !!! note 
-    If you are using `decodeStrategy: Auto` and start to see ESO pulling completely wrong secret values into your kubernetes secret, consider changing it to `None` to investigate it.
+    If you are using `decodeStrategy: Auto` and start to see ESO pulling completely wrong secret values into your kubernetes secret, consider changing it to `None` to investigate it.

docs/guides/generator.md

@@ -9,7 +9,7 @@ These values can be used with the other features like `rewrite` or `template`. I
 Generators can be defined as a custom resource and re-used across different ExternalSecrets. **Every invocation creates a new set of values**. I.e. you can not share the same value produced by a generator across different `ExternalSecrets` or `spec.dataFrom[]` entries.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: "ecr-token"

docs/guides/security-best-practices.md

@@ -18,7 +18,7 @@ For cluster-wide resources like `ClusterSecretStore` and `ClusterExternalSecret`
 Utilize the ClusterSecretStore resource to define specific match conditions using `namespaceSelector` or an explicit namespaces list. This restricts the usage of the `ClusterSecretStore` to a predetermined list of namespaces or a namespace that matches a predefined label. Here's an example:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: fake

docs/guides/v1beta1.md

@@ -34,4 +34,4 @@ If you already have an installation of ESO using `v1alpha1`, we recommend you to
 
 If you are installing CRDs manually, you will need to deploy the bundle CRD file available at `deploys/crds/bundle.yaml`. This bundle file contains `v1beta1` definition and a conversion webhook configuration. This configuration will ensure that new requests to handle any CRD object will only be valid after the upgrade is successfully complete - so there are no risks of losing data due to an incomplete upgrade. Once the new CRDs are applied, you can proceed to upgrade the controller version.
 
-Once the upgrade is finished, at each reconcile, any `ExternalSecret`, `SecretStore`,  and `ClusterSecretStore` stored in `v1alpha1` will be automatically converted to `v1beta1`. 
+Once the upgrade is finished, at each reconcile, any `ExternalSecret`, `SecretStore`,  and `ClusterSecretStore` stored in `v1alpha1` will be automatically converted to `v1beta1`. 

docs/introduction/deprecation-policy.md

@@ -44,4 +44,4 @@ This includes, but insn't limited to :
 
 ## Depreaction Process:
 
-Deprecation process is described within the [project github repository](https://github.com/external-secrets/external-secrets/blob/main/DEPRECATING.md)
+Deprecation process is described within the [project github repository](https://github.com/external-secrets/external-secrets/blob/main/DEPRECATING.md)

docs/introduction/prerequisites.md

@@ -236,4 +236,4 @@ Please consult the <a href="https://go.dev/doc/install">official documentation</
   <h3>How to Install Tilt</h3>
 
   <p>Please consult the <a href="https://docs.tilt.dev/install.html">official Tilt installation guide</a>.</p>
-</details>
+</details>

docs/provider/alibaba.md

@@ -24,7 +24,7 @@ data:
 ```
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secretstore-sample
@@ -64,7 +64,7 @@ extraVolumeMounts:
 
 and provide the RAM role ARN and OIDC volume path to the secret store
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secretstore-sample
@@ -85,7 +85,7 @@ spec:
 To create a kubernetes secret from the Alibaba Cloud Key Management Service secret a `Kind=ExternalSecret` is needed.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example

docs/provider/aws-parameter-store.md

@@ -79,7 +79,7 @@ Consider the following JSON object that is stored in the Parameter Store key `fr
 This is an example on how you would look up nested keys in the above json object:
 
 ``` yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: extract-data

docs/provider/aws-secrets-manager.md

@@ -165,7 +165,7 @@ The `version` field on the `remoteRef` of the ExternalSecret will normally consi
 So in this example, the operator will request the same secret with different versions: `AWSCURRENT` and `AWSPREVIOUS`:
 
 ``` yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: versioned-api-key
@@ -191,7 +191,7 @@ spec:
 While in this example, the operator will request the secret with `VersionId` as `abcd-1234`
 
 ``` yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: versioned-api-key

docs/provider/azure-key-vault.md

@@ -14,7 +14,7 @@ Since the [AAD Pod Identity](https://azure.github.io/aad-pod-identity/docs/) is
 We support connecting to different cloud flavours azure supports: `PublicCloud`, `USGovernmentCloud`, `ChinaCloud` and `GermanCloud`. You have to specify the `environmentType` and point to the correct cloud flavour. This defaults to `PublicCloud`.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: azure-backend

docs/provider/beyondtrust.md

@@ -67,7 +67,7 @@ kubectl apply -f secret-store.yml
 ```
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secretstore-beyondtrust
@@ -80,7 +80,7 @@ spec:
         verifyCA: true
         clientTimeOutSeconds: 45
         apiVersion: "3.0" # The recommended version is 3.1. If no version is specified, the default API version 3.0 will be used.
-      auth: 
+      auth:
         certificate: # omit certificates if retrievalType is SECRET
           secretRef:
             name: bt-certificate
@@ -113,7 +113,7 @@ kubectl apply -f external-secret.yml
 ```
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: beyondtrust-external-secret
@@ -136,4 +136,4 @@ spec:
 ```shell
 # WARNING: this command will reveal the stored secret in plain text
 kubectl get secret my-beyondtrust-secret -o jsonpath="{.data.secretKey}" | base64 --decode && echo
-```
+```

docs/provider/bitwarden-secrets-manager.md

@@ -67,7 +67,7 @@ There are two ways to fetch secrets from the provider.
 In order to fetch a secret by using its UUID simply provide that as remote key in the external secrets like this:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: bitwarden
@@ -93,7 +93,7 @@ To find a secret using its name, we need a bit more information. Mainly, these a
 - if more than one name exists for the same projectID within the same organization we error
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: bitwarden

docs/provider/chef.md

@@ -4,7 +4,7 @@
 
 In many enterprises, legacy applications and infrastructure are still tightly integrated with the Chef/Chef Infra Server/Chef Server Cluster for configuration and secrets management. Teams often rely on [Chef data bags](https://docs.chef.io/data_bags/) to securely store sensitive information such as application secrets and infrastructure configurations. These data bags serve as a centralized repository for managing and distributing sensitive data across the Chef ecosystem.
 
-**NOTE:** `Chef External Secrets provider` is designed only to fetch data from the Chef data bags into Kubernetes secrets, it won't update/delete any item in the data bags. 
+**NOTE:** `Chef External Secrets provider` is designed only to fetch data from the Chef data bags into Kubernetes secrets, it won't update/delete any item in the data bags.
 
 ### Authentication
 
@@ -30,7 +30,7 @@ kubectl create secret generic chef-user-secret -n vivid --from-literal=user-priv
 The Chef `ClusterSecretStore` is a cluster-scoped SecretStore that can be referenced by all Chef `ExternalSecrets` from all namespaces. You can follow the below example to create a `ClusterSecretStore` resource.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: vivid-clustersecretstore # name of ClusterSecretStore
@@ -54,7 +54,7 @@ Chef `SecretStores` are bound to a namespace and can not reference resources acr
 You can follow the below example to create a `SecretStore` resource.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: vivid-secretstore # name of SecretStore
@@ -86,7 +86,7 @@ When the above `ClusterSecretStore` and `ExternalSecret` resources are created,
 
 To get all data items inside the data bag, you can use the `dataFrom` directive:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vivid-external-secrets # name of ExternalSecret

docs/provider/cloudru.md

@@ -89,7 +89,7 @@ curl --location 'https://secretmanager.api.cloud.ru/v1/secrets' \
     * `key_secret` is the AccessKey key_secret
 * Create a [SecretStore](../api/secretstore.md) pointing to `csm-secret` k8s Secret:
     ```yaml
-    apiVersion: external-secrets.io/v1beta1
+    apiVersion: external-secrets.io/v1
     kind: SecretStore
     metadata:
       name: csm
@@ -113,7 +113,7 @@ curl --location 'https://secretmanager.api.cloud.ru/v1/secrets' \
 #### Create an [ExternalSecret](../api/externalsecret.md) pointing to SecretStore.
   * Classic, non-json:
     ```yaml
-    apiVersion: external-secrets.io/v1beta1
+    apiVersion: external-secrets.io/v1
     kind: ExternalSecret
     metadata:
       name: csm-ext-secret
@@ -133,7 +133,7 @@ curl --location 'https://secretmanager.api.cloud.ru/v1/secrets' \
   * From Multi KeyValue, value MUST be in **json format**:
   NOTE: You can use *either* `name` or `tags` to filter the secrets. Here are basic examples of both:
     ```yaml
-    apiVersion: external-secrets.io/v1beta1
+    apiVersion: external-secrets.io/v1
     kind: ExternalSecret
     metadata:
       name: csm-ext-secret
@@ -154,7 +154,7 @@ curl --location 'https://secretmanager.api.cloud.ru/v1/secrets' \
 
   * With all fields, value MUST be in **json format**:
     ```yaml
-    apiVersion: external-secrets.io/v1beta1
+    apiVersion: external-secrets.io/v1
     kind: ExternalSecret
     metadata:
       name: csm-ext-secret
@@ -172,7 +172,7 @@ curl --location 'https://secretmanager.api.cloud.ru/v1/secrets' \
     ```
   * Search the secrets by the Name or Labels (tags):
     ```yaml
-    apiVersion: external-secrets.io/v1beta1
+    apiVersion: external-secrets.io/v1
     kind: ExternalSecret
     metadata:
       name: csm-ext-secret

docs/provider/delinea.md

@@ -12,7 +12,7 @@ Both client ID and client secret can be specified either directly in the config,
 To acquire client ID and client secret, refer to the  [policy management](https://docs.delinea.com/dsv/current/tutorials/policy.md) and [client management](https://docs.delinea.com/dsv/current/usage/cli-ref/client.md) documentation.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-store
@@ -42,7 +42,7 @@ Secrets can be referenced by path. Getting a specific version of a secret is not
 Note that because all DSV secrets are JSON objects, you must specify `remoteRef.property`. You can access nested values or arrays using [gjson syntax](https://github.com/tidwall/gjson/blob/master/SYNTAX.md).
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
     name: secret

docs/provider/device42.md

@@ -18,7 +18,7 @@ data:
 ### Creating a SecretStore
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: device42-secret-store
@@ -40,7 +40,7 @@ Secrets can be referenced by defining the `key` containing the Id of the secret.
 The `password` field is return from device42
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: device42-external-secret

docs/provider/fortanix.md

@@ -9,7 +9,7 @@ SDKMS [Application API Key](https://support.fortanix.com/hc/en-us/articles/36001
 ### Creating a SecretStore
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-store
@@ -27,7 +27,7 @@ spec:
 
 ```yaml
 # Raw stored value
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: secret
@@ -42,7 +42,7 @@ spec:
       key: <SDKMS_SECURITY_OBJECT_NAME>
 ---
 # From stored key-value JSON
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: secret-from-property
@@ -58,7 +58,7 @@ spec:
       property: <SECURITY_OBJECT_VALUE_INNER_PROPERTY>
 ---
 # Extract all keys from stored key-value JSON
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: secret-from-extract

docs/provider/google-secrets-manager.md

@@ -342,7 +342,7 @@ spec:
 Note: When using CMEK, you must specify a location in the SecretStore as customer-managed encryption keys are region-specific.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: gcp-secret-store

docs/provider/hashicorp-vault.md

@@ -13,7 +13,7 @@ one supported by this provider. For other secrets engines, please refer to the
 First, create a SecretStore with a vault backend. For the sake of simplicity we'll use a static token `root`:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: vault-backend
@@ -58,7 +58,7 @@ If you are using version: 1, just remember to update your SecretStore manifest a
 Now create a ExternalSecret that uses the above SecretStore:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vault-example
@@ -105,7 +105,7 @@ Keep in mind that fetching the labels with `metadataPolicy: Fetch` only works wi
 You can fetch all key/value pairs for a given path If you leave the `remoteRef.property` empty. This returns the json-encoded secret value for that path.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vault-example
@@ -134,7 +134,7 @@ Given the following secret - assume its path is `/dev/config`:
 
 You can set the `remoteRef.property` to point to the nested key using a [gjson](https://github.com/tidwall/gjson) expression.
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vault-example
@@ -170,7 +170,7 @@ Given the following secret - assume its path is `/dev/config`:
 
 You can set the `remoteRef.property` to point to the nested key using a [gjson](https://github.com/tidwall/gjson) expression.
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vault-example
@@ -220,7 +220,7 @@ Also consider the following secret has the following `custom_metadata`:
 
 It is possible to find this secret by all the following possibilities:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vault-example
@@ -243,7 +243,7 @@ will generate a secret with:
 
 Currently, `Find` operations are recursive throughout a given vault folder, starting on `provider.Path` definition. It is recommended to narrow down the scope of search by setting a `find.path` variable. This is also useful to automatically reduce the resulting secret key names:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vault-example
@@ -448,7 +448,7 @@ and pick the best fit for your environment and Vault configuration.
 [Vault namespaces](https://www.vaultproject.io/docs/enterprise/namespaces) are an enterprise feature that support multi-tenancy. You can specify a vault namespace using the `namespace` property when you define a SecretStore:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: vault-backend
@@ -469,7 +469,7 @@ spec:
 In some situations your authentication backend may be in one namespace, and your secrets in another. You can authenticate into one namespace, and use that token against another, by setting `provider.vault.namespace` and `provider.vault.auth.namespace` to different values. If `provider.vault.auth.namespace` is unset but `provider.vault.namespace` is, it will default to the `provider.vault.namespace` value.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: vault-backend

docs/provider/kubernetes.md

@@ -9,7 +9,7 @@ The `SecretStore` reconciler checks if you have read access for secrets in that
 This provider supports the use of the `Property` field. With it you point to the key of the remote secret. If you leave it empty it will json encode all key/value pairs.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: database-credentials
@@ -58,7 +58,7 @@ spec:
 You can fetch secrets based on labels or names matching a regexp:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: fetch-tls-and-nginx
@@ -89,7 +89,7 @@ If you want to connect to a remote API Server you need to fetch it and store it
 You may also define it inline as base64 encoded value using the `caBundle` property.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: k8s-store-default-ns
@@ -150,7 +150,7 @@ data:
 Create a SecretStore: The `auth` section indicates that the type `token` will be used for authentication, it includes the path to fetch the token. Set `remoteNamespace` to the name of the namespace where your target secrets reside.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: k8s-store-token-auth
@@ -185,7 +185,7 @@ $ kubectl create rolebinding my-store --role=eso-store-role --serviceaccount=def
 Create a SecretStore: the `auth` section indicates that the type `serviceAccount` will be used for authentication.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: k8s-store-sa-auth
@@ -212,7 +212,7 @@ $ kubectl create secret tls tls-secret --cert=path/to/tls.cert --key=path/to/tls
 Reference the `tls-secret` in the SecretStore
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: k8s-store-cert-auth
@@ -302,7 +302,7 @@ metadata:
 stringData:
   token: "<paste-bearer-token-here>"
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: kubernetes-secret-store
@@ -323,7 +323,7 @@ spec:
             name: eso-token
             key: token
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: eso-kubernetes-secret

docs/provider/previder.md

@@ -25,7 +25,7 @@ data:
 ```
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: previder-secretstore-sample
@@ -45,7 +45,7 @@ spec:
 To create a kubernetes secret from the Previder Secret Vault, create an ExternalSecret with a reference to a Vault secret.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example

docs/provider/pulumi.md

@@ -15,7 +15,7 @@ Pulumi [Access Tokens](https://www.pulumi.com/docs/pulumi-cloud/access-managemen
 A Pulumi `SecretStore` can be created by specifying the `organization`, `project` and `environment` and referencing a Kubernetes secret containing the `accessToken`.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-store
@@ -38,7 +38,7 @@ If required, the API URL (`apiUrl`) can be customized as well. If not specified,
 Similarly, a `ClusterSecretStore` can be created by specifying the `namespace` and referencing a Kubernetes secret containing the `accessToken`.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: secret-store
@@ -60,7 +60,7 @@ spec:
 Secrets can be referenced by defining the `key` containing the JSON path to the secret. Pulumi ESC secrets are internally organized as a JSON object.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: secret

docs/provider/scaleway.md

@@ -9,7 +9,7 @@ Both access and secret keys can be specified either directly in the config, or b
 a kubernetes secret.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-store
@@ -33,7 +33,7 @@ Secrets can be referenced by name, id or path, using the prefixes `"name:"`, `"i
 A PushSecret resource can only use a name reference.
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
     name: secret

docs/provider/secretserver.md

@@ -18,7 +18,7 @@ spec.provider.secretserver.password.value: "yourpassword" <br />
 Or you can reference a kubernetes secret (password example below).
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-server-store
@@ -48,7 +48,7 @@ in your ExternalSecret configuration.<br />
 You can access nested values or arrays using [gjson syntax](https://github.com/tidwall/gjson/blob/master/SYNTAX.md).
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
     name: secret-server-external-secret

docs/provider/webhook.md

@@ -8,7 +8,7 @@ First, create a SecretStore with a webhook backend.  We'll use a static user/pas
 
 ```yaml
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: webhook-backend
@@ -45,7 +45,7 @@ NB: This is obviously not practical because it just returns the key as the resul
 Now create an ExternalSecret that uses the above SecretStore:
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: webhook-example
@@ -74,7 +74,7 @@ To push a secret, create the following store:
 
 ```yaml
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: webhook-backend
@@ -125,7 +125,7 @@ Webhook also supports using NTLM for authorization:
 
 ```yaml
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: webhook-backend
@@ -175,7 +175,7 @@ Each secret has a `name` property which determines the name of the object in the
 ### All Parameters
 
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: statervault

docs/provider/yandex-certificate-manager.md

@@ -26,7 +26,7 @@ kubectl create secret generic yc-auth --from-file=authorized-key=authorized-key.
 ```
 * Create a [SecretStore](../api/secretstore.md) pointing to `yc-auth` k8s secret:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-store
@@ -60,7 +60,7 @@ yc cm certificate list-access-bindings --id *****
 ```
 * Create an [ExternalSecret](../api/externalsecret.md) pointing to `secret-store` and the certificate in Certificate Manager:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: external-secret

docs/provider/yandex-lockbox.md

@@ -26,7 +26,7 @@ kubectl create secret generic yc-auth --from-file=authorized-key=authorized-key.
 ```
 * Create a [SecretStore](../api/secretstore.md) pointing to `yc-auth` k8s secret:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secret-store
@@ -63,7 +63,7 @@ yc lockbox secret list-access-bindings --name lockbox-secret
 ```
 * Create an [ExternalSecret](../api/externalsecret.md) pointing to `secret-store` and `lockbox-secret`:
 ```yaml
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: external-secret

docs/snippets/1password-external-secret-my-cert.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: my-cert

docs/snippets/1password-external-secret-my-env-config.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: my-env-config

docs/snippets/1password-secret-store.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: staging

docs/snippets/akeyless-external-secret-json.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: database-credentials

docs/snippets/akeyless-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: database-credentials

docs/snippets/akeyless-secret-store-k8s-auth.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: akeyless-secret-store

docs/snippets/akeyless-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: akeyless-secret-store

docs/snippets/aws-anchore-engine-access-credentials-external-secret.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: anchore-access-credentials

docs/snippets/aws-jenkins-credential-github-ssh-external-secret.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: github-ssh-access

docs/snippets/aws-jenkins-credential-sonarqube-api-token-external-secret.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: sonarqube-api-token

docs/snippets/aws-jenkins-credentials-harbor-chart-robot-external-secret.yaml

@@ -1,5 +1,5 @@
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: harbor-chart-robot
@@ -25,4 +25,4 @@ spec:
     - secretKey: username
       remoteRef:
         key: service/harbor/chartRobot
-        property: username
+        property: username

docs/snippets/aws-parameter-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: parameterstore

docs/snippets/aws-sm-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example

docs/snippets/aws-sm-store-secretsmanager-config.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: aws-secretsmanager

docs/snippets/aws-sm-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: aws-secretsmanager

docs/snippets/azkv-datafrom-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: all-secrets
@@ -28,4 +28,4 @@ spec:
   # and store them as individual keys in a secret
   - extract:
       key: database-credentials
-      metadataPolicy: Fetch
+      metadataPolicy: Fetch

docs/snippets/azkv-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: database-credentials
@@ -46,4 +46,4 @@ spec:
   # the key is returned PEM encoded
   - secretKey: encryption-pubkey
     remoteRef:
-      key: key/encryption-pubkey
+      key: key/encryption-pubkey

docs/snippets/azkv-pkcs12-cert-external-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: tls-client-credentials

docs/snippets/azkv-pushsecret-key.yaml

@@ -23,4 +23,4 @@ spec:
     - match:
         secretKey: tls.key # Source Kubernetes secret key containing the JWK
         remoteRef:
-          remoteKey: key/my-azkv-key-name
+          remoteKey: key/my-azkv-key-name

docs/snippets/azkv-secret-store-mi.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: azure-store

docs/snippets/azkv-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: azure-store

docs/snippets/azkv-workload-identity-mounted.yaml

@@ -7,7 +7,7 @@ metadata:
     azure.workload.identity/client-id: 7d8cdf74-xxxx-xxxx-xxxx-274d963d358b
     azure.workload.identity/tenant-id: 5a02a20e-xxxx-xxxx-xxxx-0ad5b634c5d8
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: azure-store
@@ -16,4 +16,4 @@ spec:
     azurekv:
       authType: WorkloadIdentity
       vaultUrl: "https://xx-xxxx-xx.vault.azure.net"
-      # note: no serviceAccountRef was provided
+      # note: no serviceAccountRef was provided

docs/snippets/azkv-workload-identity-secretref.yaml

@@ -5,7 +5,7 @@ metadata:
   name: workload-identity-sa
   annotations: {}
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: azure-store

docs/snippets/azkv-workload-identity.yaml

@@ -7,7 +7,7 @@ metadata:
     azure.workload.identity/client-id: 7d8cdf74-xxxx-xxxx-xxxx-274d963d358b
     azure.workload.identity/tenant-id: 5a02a20e-xxxx-xxxx-xxxx-0ad5b634c5d8
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: azure-store

docs/snippets/basic-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example

docs/snippets/basic-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: secretstore-sample

docs/snippets/beyondtrust-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
  name: beyondtrust-external-secret
@@ -13,4 +13,4 @@ spec:
  data:
    - secretKey: secretKey
      remoteRef:
-       key: system01/managed_account01
+       key: system01/managed_account01

docs/snippets/beyondtrust-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
  name: secretstore-beyondtrust
@@ -31,4 +31,4 @@ spec:
       verifyCA: true
       clientTimeOutSeconds: 45
       apiUrl: https://example.ps-dev.beyondtrustcloud.com:443/BeyondTrust/api/public/v3/
-      apiVersion: "3.1"
+      apiVersion: "3.1"

docs/snippets/bitwarden-secret-store.yaml

@@ -1,6 +1,6 @@
 {% raw %}
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: bitwarden-login
@@ -13,7 +13,7 @@ spec:
       result:
         jsonPath: "$.data.login.{{ .remoteRef.property }}"
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: bitwarden-fields
@@ -24,7 +24,7 @@ spec:
       result:
         jsonPath: "$.data.fields[?@.name==\"{{ .remoteRef.property }}\"].value"
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: bitwarden-notes
@@ -35,7 +35,7 @@ spec:
       result:
         jsonPath: "$.data.notes"
 ---
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: bitwarden-attachments

docs/snippets/bitwarden-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: my-secrets

docs/snippets/bitwarden-secrets-manager-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: bitwarden-secretsmanager

docs/snippets/chef-external-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: vivid-external-secrets # name of ExternalSecret

docs/snippets/cloak-external-secret.yaml

@@ -1,5 +1,5 @@
 # Access a secret
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: cloak-example
@@ -16,4 +16,4 @@ spec:
       key: PULUMI_ACCESS_TOKEN
   - secretKey: do-access-token
     remoteRef:
-      key: DIGITALOCEAN_ACCESS_TOKEN
+      key: DIGITALOCEAN_ACCESS_TOKEN

docs/snippets/cloak-proxy-deployment.yaml

@@ -25,4 +25,4 @@ spec:
                 name: cloak-key 
                 key: ecdh_private_key 
         ports:
-        - containerPort: 7105
+        - containerPort: 7105

docs/snippets/cloak-proxy-service.yaml

@@ -9,4 +9,4 @@ spec:
   ports:
     - protocol: TCP
       port: 7105
-      targetPort: 7105
+      targetPort: 7105

docs/snippets/cloak-secret-store.yaml

@@ -1,6 +1,6 @@
 {% raw %}
 # An External secrets webhookl
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: cloak-backend
@@ -12,4 +12,4 @@ spec:
         jsonPath: "$.value"
       headers:
         Content-Type: application/json
-{%- endraw %}
+{%- endraw %}

docs/snippets/conjur-external-secret-find.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: conjur-find-by-name

docs/snippets/conjur-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: conjur

docs/snippets/conjur-secret-store-apikey.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: conjur

docs/snippets/conjur-secret-store-jwt-secret-ref.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: conjur

docs/snippets/conjur-secret-store-jwt-service-account-ref.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: conjur

docs/snippets/controller-class-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: controller-custom-example
@@ -14,4 +14,4 @@ spec:
       auth:
         kubernetes:
           mountPath: "kubernetes"
-          role: "demo-role"
+          role: "demo-role"

docs/snippets/dashboard.json

@@ -1958,4 +1958,4 @@
   "uid": "n4IdKaJVk",
   "version": 9,
   "weekStart": ""
-}
+}

docs/snippets/datafrom-rewrite-conflict.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example
@@ -21,4 +21,4 @@ spec:
     rewrite:
     - regexp:
         source: "(.*)"
-        target: "prod-$1"
+        target: "prod-$1"

docs/snippets/datafrom-rewrite-invalid-characters.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example
@@ -15,4 +15,4 @@ spec:
     rewrite:
     - regexp:
         source: "[^a-zA-Z0-9 -]"
-        target: "_"
+        target: "_"

docs/snippets/datafrom-rewrite-remove-path.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example
@@ -17,4 +17,4 @@ spec:
     rewrite:
     - regexp:
         source: "path/to/my/secrets/(.*)"
-        target: "$1"
+        target: "$1"

docs/snippets/device42-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: device42-find-by-id

docs/snippets/doppler-fetch-all-secrets.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: auth-api-all

docs/snippets/doppler-fetch-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: auth-api-db-url

docs/snippets/doppler-filtered-secrets.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: auth-api-db

docs/snippets/doppler-generic-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: doppler-auth-api

docs/snippets/doppler-name-transformer-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: doppler-auth-api-dotnet-env

docs/snippets/doppler-name-transformer-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: doppler-auth-api-dotnet-env

docs/snippets/doppler-parse-json-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: auth-api-sa-json

docs/snippets/doppler-secrets-download-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: auth-api-json-file

docs/snippets/doppler-secrets-download-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: doppler-auth-api-json-file

docs/snippets/fake-provider-es.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example
@@ -17,4 +17,4 @@ spec:
   dataFrom:
   - extract:
       key: /foo/baz
-      version: v1
+      version: v1

docs/snippets/fake-provider-secret.yaml

@@ -5,4 +5,4 @@ metadata:
   namespace: default
 data:
   foo_bar: SEVMTE8x # HELLO1  (via data)
-  john: ZG9l #doe (via dataFrom)
+  john: ZG9l #doe (via dataFrom)

docs/snippets/fake-provider-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: fake
@@ -14,4 +14,4 @@ spec:
         version: "v2"
       - key: "/foo/baz"
         value: '{"john": "doe"}'
-        version: "v1"
+        version: "v1"

docs/snippets/filtercertchain-template-v2-external-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: template

docs/snippets/filterpem-template-v2-external-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: template

docs/snippets/full-cluster-external-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterExternalSecret
 metadata:
   name: "hello-world"

docs/snippets/full-cluster-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ClusterSecretStore
 metadata:
   name: example

docs/snippets/full-external-secret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: "hello-world"

docs/snippets/full-secret-store.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: SecretStore
 metadata:
   name: example

docs/snippets/gcpsm-data-from-external-secret.yaml

@@ -1,4 +1,4 @@
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: example

docs/snippets/gcpsm-docker-config-externalsecret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: dk-cfg-example

docs/snippets/gcpsm-docker-config-helm-externalsecret.yaml

@@ -1,5 +1,5 @@
 {% raw %}
-apiVersion: external-secrets.io/v1beta1
+apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
   name: dk-cfg-example