diff --git a/Cargo.lock b/Cargo.lock index 315632080..1dcf864bd 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -311,7 +311,7 @@ checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe" [[package]] name = "agent" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-debug-echo", "akri-discovery-utils", @@ -376,7 +376,7 @@ dependencies = [ [[package]] name = "akri-debug-echo" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "akri-shared", @@ -395,7 +395,7 @@ dependencies = [ [[package]] name = "akri-discovery-utils" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-shared", "anyhow", @@ -415,7 +415,7 @@ dependencies = [ [[package]] name = "akri-onvif" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "akri-shared", @@ -443,7 +443,7 @@ dependencies = [ [[package]] name = "akri-opcua" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "akri-shared", @@ -466,7 +466,7 @@ dependencies = [ [[package]] name = "akri-shared" -version = "0.6.2" +version = "0.6.3" dependencies = [ "anyhow", "async-trait", @@ -495,7 +495,7 @@ dependencies = [ [[package]] name = "akri-udev" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "anyhow", @@ -1036,7 +1036,7 @@ checksum = "245097e9a4535ee1e3e3931fcfcd55a796a44c643e8596ff6566d68f09b87bbc" [[package]] name = "controller" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-shared", "anyhow", @@ -1203,7 +1203,7 @@ dependencies = [ [[package]] name = "debug-echo-discovery-handler" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-debug-echo", "akri-discovery-utils", @@ -2382,7 +2382,7 @@ checksum = "af8b08b04175473088b46763e51ee54da5f9a164bc162f615b91bc179dbf15a3" [[package]] name = "onvif-discovery-handler" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "akri-onvif", @@ -2448,7 +2448,7 @@ dependencies = [ [[package]] name = "opcua-discovery-handler" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "akri-opcua", @@ -4516,7 +4516,7 @@ dependencies = [ [[package]] name = "udev-discovery-handler" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-discovery-utils", "akri-udev", @@ -4527,7 +4527,7 @@ dependencies = [ [[package]] name = "udev-video-broker" -version = "0.6.2" +version = "0.6.3" dependencies = [ "akri-shared", "env_logger", @@ -4821,7 +4821,7 @@ dependencies = [ [[package]] name = "webhook-configuration" -version = "0.6.2" +version = "0.6.3" dependencies = [ "actix", "actix-rt", diff --git a/agent/Cargo.toml b/agent/Cargo.toml index c6835794c..9e4320336 100644 --- a/agent/Cargo.toml +++ b/agent/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "agent" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring ", ""] edition = "2018" diff --git a/controller/Cargo.toml b/controller/Cargo.toml index f802cc850..7fb3db5f6 100644 --- a/controller/Cargo.toml +++ b/controller/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "controller" -version = "0.6.2" +version = "0.6.3" authors = [""] edition = "2018" diff --git a/deployment/helm/Chart.yaml b/deployment/helm/Chart.yaml index b3dfd1b75..3797aaa82 100644 --- a/deployment/helm/Chart.yaml +++ b/deployment/helm/Chart.yaml @@ -15,9 +15,9 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 0.6.2 +version: 0.6.3 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. -appVersion: 0.6.2 +appVersion: 0.6.3 diff --git a/deployment/helm/templates/custom.yaml b/deployment/helm/templates/custom-configuration.yaml similarity index 100% rename from deployment/helm/templates/custom.yaml rename to deployment/helm/templates/custom-configuration.yaml diff --git a/deployment/helm/templates/debug-echo.yaml b/deployment/helm/templates/debug-echo-configuration.yaml similarity index 100% rename from deployment/helm/templates/debug-echo.yaml rename to deployment/helm/templates/debug-echo-configuration.yaml diff --git a/deployment/helm/templates/onvif.yaml b/deployment/helm/templates/onvif-configuration.yaml similarity index 100% rename from deployment/helm/templates/onvif.yaml rename to deployment/helm/templates/onvif-configuration.yaml diff --git a/deployment/helm/templates/opcua.yaml b/deployment/helm/templates/opcua-configuration.yaml similarity index 100% rename from deployment/helm/templates/opcua.yaml rename to deployment/helm/templates/opcua-configuration.yaml diff --git a/deployment/helm/templates/udev.yaml b/deployment/helm/templates/udev-configuration.yaml similarity index 100% rename from deployment/helm/templates/udev.yaml rename to deployment/helm/templates/udev-configuration.yaml diff --git a/deployment/helm/values.yaml b/deployment/helm/values.yaml index 17609f2e8..d9e4bf490 100644 --- a/deployment/helm/values.yaml +++ b/deployment/helm/values.yaml @@ -233,7 +233,7 @@ debugEcho: # repository is the container reference repository: ghcr.io/deislabs/akri/debug-echo-discovery # tag is the container tag - # debugEcho.yaml will default to v(AppVersion)[-dev] + # debug-echo-configuration.yaml will default to v(AppVersion)[-dev] # with `-dev` added if `useDevelopmentContainers` is specified tag: # pullPolicy is the pull policy @@ -320,7 +320,7 @@ onvif: # repository is the container reference repository: ghcr.io/deislabs/akri/onvif-discovery # tag is the container tag - # onvif.yaml will default to v(AppVersion)[-dev] + # onvif-configuration.yaml will default to v(AppVersion)[-dev] # with `-dev` added if `useDevelopmentContainers` is specified tag: # pullPolicy is the pull policy @@ -405,7 +405,7 @@ opcua: # repository is the container reference repository: ghcr.io/deislabs/akri/opcua-discovery # tag is the container tag - # opcua.yaml will default to v(AppVersion)[-dev] + # opcua-configuration.yaml will default to v(AppVersion)[-dev] # with `-dev` added if `useDevelopmentContainers` is specified tag: # pullPolicy is the pull policy @@ -482,7 +482,7 @@ udev: # repository is the container reference repository: ghcr.io/deislabs/akri/udev-discovery # tag is the container tag - # udev.yaml will default to v(AppVersion)[-dev] + # udev-configuration.yaml will default to v(AppVersion)[-dev] # with `-dev` added if `useDevelopmentContainers` is specified tag: # pullPolicy is the pull policy diff --git a/discovery-handler-modules/debug-echo-discovery-handler/Cargo.toml b/discovery-handler-modules/debug-echo-discovery-handler/Cargo.toml index 8c2aa77fb..9e17ab0e8 100644 --- a/discovery-handler-modules/debug-echo-discovery-handler/Cargo.toml +++ b/discovery-handler-modules/debug-echo-discovery-handler/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "debug-echo-discovery-handler" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handler-modules/onvif-discovery-handler/Cargo.toml b/discovery-handler-modules/onvif-discovery-handler/Cargo.toml index 9e66d15f9..504890b6f 100644 --- a/discovery-handler-modules/onvif-discovery-handler/Cargo.toml +++ b/discovery-handler-modules/onvif-discovery-handler/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "onvif-discovery-handler" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handler-modules/opcua-discovery-handler/Cargo.toml b/discovery-handler-modules/opcua-discovery-handler/Cargo.toml index 8be627f7f..e20b79a63 100644 --- a/discovery-handler-modules/opcua-discovery-handler/Cargo.toml +++ b/discovery-handler-modules/opcua-discovery-handler/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "opcua-discovery-handler" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handler-modules/udev-discovery-handler/Cargo.toml b/discovery-handler-modules/udev-discovery-handler/Cargo.toml index 6d3bf76a7..4a0791ad7 100644 --- a/discovery-handler-modules/udev-discovery-handler/Cargo.toml +++ b/discovery-handler-modules/udev-discovery-handler/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "udev-discovery-handler" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handlers/debug-echo/Cargo.toml b/discovery-handlers/debug-echo/Cargo.toml index cdbe26128..5472b6cda 100644 --- a/discovery-handlers/debug-echo/Cargo.toml +++ b/discovery-handlers/debug-echo/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "akri-debug-echo" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handlers/onvif/Cargo.toml b/discovery-handlers/onvif/Cargo.toml index b4df49be1..6b6601572 100644 --- a/discovery-handlers/onvif/Cargo.toml +++ b/discovery-handlers/onvif/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "akri-onvif" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handlers/opcua/Cargo.toml b/discovery-handlers/opcua/Cargo.toml index 05fcca7e1..58a72f855 100644 --- a/discovery-handlers/opcua/Cargo.toml +++ b/discovery-handlers/opcua/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "akri-opcua" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-handlers/udev/Cargo.toml b/discovery-handlers/udev/Cargo.toml index 2d1ec5e8d..6f9997cc3 100644 --- a/discovery-handlers/udev/Cargo.toml +++ b/discovery-handlers/udev/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "akri-udev" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/discovery-utils/Cargo.toml b/discovery-utils/Cargo.toml index 655188642..a7cc6f421 100644 --- a/discovery-utils/Cargo.toml +++ b/discovery-utils/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "akri-discovery-utils" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring "] edition = "2018" diff --git a/docs/architecture.md b/docs/architecture.md index 64ae5e1c1..237eb6950 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -15,7 +15,7 @@ The configuration of Akri is enabled by the Configuration CRD. Akri users will * a ServiceSpec (spec.instanceServiceSpec) that defines the service that provides a single stable endpoint to access each individual resource's set of broker pods. * a ServiceSpec (spec.configurationServiceSpec) that defines the service that provides a single stable endpoint to access the set of all brokers for all resources associated with the Configuration. -Akri has already provided two Configurations, one for discovering IP cameras using the ONVIF protocol and the other for discovering USB cameras via udev. Let's look at an [example ONVIF Configuration yaml](../test/yaml/akri-onvif-video.yaml). You can see it specifies the protocol ONVIF, an image for the broker pod, a capacity of 5, and two Kubernetes services. In this case, the broker pod is a sample frame server we have provided. To get only the frames from a specific camera, a user could point an application at the Instance service, while the Configuration service provides the frames from all the cameras.The ONVIF Configuration can be customized using Helm. When installing the ONVIF Configuration to your Akri enabled cluster, you can specify [the values](../deployment/helm/values.yaml) you want to be inserted into the [ONVIF Configuration template](../deployment/helm/templates/onvif.yaml). Learn more about [deploying the ONVIF sample here](./onvif-configuration.md). +Akri has already provided two Configurations, one for discovering IP cameras using the ONVIF protocol and the other for discovering USB cameras via udev. Let's look at an [example ONVIF Configuration yaml](../test/yaml/akri-onvif-video-configuration.yaml). You can see it specifies the protocol ONVIF, an image for the broker pod, a capacity of 5, and two Kubernetes services. In this case, the broker pod is a sample frame server we have provided. To get only the frames from a specific camera, a user could point an application at the Instance service, while the Configuration service provides the frames from all the cameras.The ONVIF Configuration can be customized using Helm. When installing the ONVIF Configuration to your Akri enabled cluster, you can specify [the values](../deployment/helm/values.yaml) you want to be inserted into the [ONVIF Configuration template](../deployment/helm/templates/onvif-configuration.yaml). Learn more about [deploying the ONVIF sample here](./onvif-configuration.md). ### Akri Instance CRD Each Instance represents an individual resource that is visible to the cluster. So, if there are 5 IP cameras visible to the cluster, there will be 5 Instances. Akri coordination and resource sharing is enabled by the Instance CRD. These instances store internal Akri state and are not intended to be edited by users. For a more in-depth understanding on how resource sharing is accomplished, see [Resource Sharing In-depth](./resource-sharing-in-depth.md). diff --git a/docs/end-to-end-demo-rpi4.md b/docs/end-to-end-demo-rpi4.md index e40d1a89a..2749ad136 100644 --- a/docs/end-to-end-demo-rpi4.md +++ b/docs/end-to-end-demo-rpi4.md @@ -98,7 +98,7 @@ You tell Akri what you want to find with an Akri Configuration, which is one of For this demo, we will specify (1) Akri's udev Discovery Handler, which is used to discover devices in the Linux device file system. Akri's udev Discovery Handler supports (2) filtering by udev rules. We want to find all video devices in the Linux device file system, which can be specified with the udev rule `KERNEL=="video[0-9]*"`. Say we wanted to be more specific and only discover devices made by Great Vendor, we could adjust our rule to be `KERNEL=="video[0-9]*"\, ENV{ID_VENDOR}=="Great Vendor"`. For (3) a broker Pod image, we will use a sample container that Akri has provided that pulls frames from the cameras and serves them over gRPC. -All of Akri's components can be deployed by specifying values in its Helm chart during an installation. Instead of having to build a Configuration from scratch, Akri has provided [Helm templates](../deployment/helm/templates) for Configurations for each supported Discovery Handler. Lets customize the generic [udev Configuration Helm template](../deployment/helm/templates/udev.yaml) with our three specifications above. We can also set the name for the Configuration to be `akri-udev-video`. +All of Akri's components can be deployed by specifying values in its Helm chart during an installation. Instead of having to build a Configuration from scratch, Akri has provided [Helm templates](../deployment/helm/templates) for Configurations for each supported Discovery Handler. Lets customize the generic [udev Configuration Helm template](../deployment/helm/templates/udev-configuration.yaml) with our three specifications above. We can also set the name for the Configuration to be `akri-udev-video`. In order for the Agent to know how to discover video devices, the udev Discovery Handler must exist. Akri supports an Agent image that includes all supported Discovery Handlers. This Agent will be used if `agent.full=true` is set. By default, a slim Agent without any embedded Discovery Handlers is deployed and the required Discovery Handlers can be deployed as DaemonSets. This demo will use that strategy, deploying the udev Discovery Handlers by specifying `udev.discovery.enabled=true` when installing Akri. diff --git a/docs/end-to-end-demo.md b/docs/end-to-end-demo.md index f357f6a34..5173ee7de 100644 --- a/docs/end-to-end-demo.md +++ b/docs/end-to-end-demo.md @@ -81,7 +81,7 @@ You tell Akri what you want to find with an Akri Configuration, which is one of For this demo, we will specify (1) Akri's udev Discovery Handler, which is used to discover devices in the Linux device file system. Akri's udev Discovery Handler supports (2) filtering by udev rules. We want to find all video devices in the Linux device file system, which can be specified with the udev rule `KERNEL=="video[0-9]*"`. Say we wanted to be more specific and only discover devices made by Great Vendor, we could adjust our rule to be `KERNEL=="video[0-9]*"\, ENV{ID_VENDOR}=="Great Vendor"`. For (3) a broker Pod image, we will use a sample container that Akri has provided that pulls frames from the cameras and serves them over gRPC. -All of Akri's components can be deployed by specifying values in its Helm chart during an installation. Instead of having to build a Configuration from scratch, Akri has provided [Helm templates](../deployment/helm/templates) for Configurations for each supported Discovery Handler. Lets customize the generic [udev Configuration Helm template](../deployment/helm/templates/udev.yaml) with our three specifications above. We can also set the name for the Configuration to be `akri-udev-video`. Also, if using MicroK8s or K3s, configure the crictl path and socket using the `AKRI_HELM_CRICTL_CONFIGURATION` variable created when setting up your cluster. +All of Akri's components can be deployed by specifying values in its Helm chart during an installation. Instead of having to build a Configuration from scratch, Akri has provided [Helm templates](../deployment/helm/templates) for Configurations for each supported Discovery Handler. Lets customize the generic [udev Configuration Helm template](../deployment/helm/templates/udev-configuration.yaml) with our three specifications above. We can also set the name for the Configuration to be `akri-udev-video`. Also, if using MicroK8s or K3s, configure the crictl path and socket using the `AKRI_HELM_CRICTL_CONFIGURATION` variable created when setting up your cluster. In order for the Agent to know how to discover video devices, the udev Discovery Handler must exist. Akri supports an Agent image that includes all supported Discovery Handlers. This Agent will be used if `agent.full=true` is set. By default, a slim Agent without any embedded Discovery Handlers is deployed and the required Discovery Handlers can be deployed as DaemonSets. This demo will use that strategy, deploying the udev Discovery Handlers by specifying `udev.discovery.enabled=true` when installing Akri. diff --git a/docs/onvif-configuration.md b/docs/onvif-configuration.md index 24c6224f7..158b99ff5 100644 --- a/docs/onvif-configuration.md +++ b/docs/onvif-configuration.md @@ -15,7 +15,7 @@ All of Akri's components can be deployed by specifying values in its Helm chart In order for the Agent to know how to discover IP cameras an ONVIF Discovery Handler must exist. Akri supports an Agent image that includes all supported Discovery Handlers. This Agent will be used if `agent.full=true`. By default, a slim Agent without any embedded Discovery Handlers is deployed and the required Discovery Handlers can be deployed as DaemonSets. This documentation will use that strategy, deploying ONVIF Discovery Handlers by specifying `onvif.discovery.enabled=true` when installing Akri. ## ONVIF Configuration Settings Instead of having to assemble your own ONVIF Configuration yaml, we have provided a [Helm -template](../deployment/helm/templates/onvif.yaml). Helm allows us to parametrize the commonly modified fields in our configuration files, and we have provided many for ONVIF (to see +template](../deployment/helm/templates/onvif-configuration.yaml). Helm allows us to parametrize the commonly modified fields in our configuration files, and we have provided many for ONVIF (to see them, run `helm inspect values akri-helm-charts/akri`). More information about the Akri Helm charts can be found in the [user guide](./user-guide.md#understanding-akri-helm-charts). To apply the ONVIF Configuration to your cluster, simply set `onvif.configuration.enabled=true` along with any of the following additional Configuration settings when installing Akri. ### Discovery Handler Discovery Details Settings diff --git a/docs/opcua-configuration.md b/docs/opcua-configuration.md index a4e079880..a19493515 100644 --- a/docs/opcua-configuration.md +++ b/docs/opcua-configuration.md @@ -9,7 +9,7 @@ In order for the Agent to know how to discover OPC UA servers an OPC UA Discover ## OPC UA Configuration Settings Instead of having to assemble your own OPC UA Configuration yaml, we have provided a [Helm -template](../deployment/helm/templates/opcua.yaml). Helm allows us to parametrize the commonly modified fields in our configuration files, and we have provided many for OPC UA (to see +template](../deployment/helm/templates/opcua-configuration.yaml). Helm allows us to parametrize the commonly modified fields in our configuration files, and we have provided many for OPC UA (to see them, run `helm inspect values akri-helm-charts/akri`). More information about the Akri Helm charts can be found in the [user guide](./user-guide.md#understanding-akri-helm-charts). To apply the OPC UA Configuration to your cluster, simply set `opcua.configuration.enabled=true` along with any of the following additional Configuration settings when installing Akri. ### Discovery Handler Discovery Details Settings diff --git a/docs/opcua-demo.md b/docs/opcua-demo.md index d61c1d3c0..520998908 100644 --- a/docs/opcua-demo.md +++ b/docs/opcua-demo.md @@ -101,7 +101,7 @@ kubectl create secret generic opcua-broker-credentials \ When mounting certificates is enabled later in the [Running Akri section](#running-akri) with Helm via `--set opcua.mountCertificates='true'`, the secret named `opcua-broker-credentials` will be mounted into the OPC UA monitoring brokers. It is mounted to the volume `credentials` at the `mountPath` /etc/opcua-certs/client-pki, as shown in the [OPC -UA Configuration Helm template](../deployment/helm/templates/opcua.yaml). This is the path where the brokers expect to +UA Configuration Helm template](../deployment/helm/templates/opcua-configuration.yaml). This is the path where the brokers expect to find the certificates. ## Creating OPC UA Servers diff --git a/samples/brokers/udev-video-broker/Cargo.toml b/samples/brokers/udev-video-broker/Cargo.toml index 423b8ba27..1674cc053 100644 --- a/samples/brokers/udev-video-broker/Cargo.toml +++ b/samples/brokers/udev-video-broker/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "udev-video-broker" -version = "0.6.2" +version = "0.6.3" authors = ["Kate Goldenring ", ""] edition = "2018" diff --git a/shared/Cargo.toml b/shared/Cargo.toml index 5d87b3d39..44126093f 100644 --- a/shared/Cargo.toml +++ b/shared/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "akri-shared" -version = "0.6.2" +version = "0.6.3" authors = [""] edition = "2018" diff --git a/shared/src/akri/configuration.rs b/shared/src/akri/configuration.rs index a3f14ad73..7b917076e 100644 --- a/shared/src/akri/configuration.rs +++ b/shared/src/akri/configuration.rs @@ -252,10 +252,10 @@ mod crd_serialization_tests { let _ = env_logger::builder().is_test(true).try_init(); let files = [ - "../test/yaml/akri-onvif-video.yaml", - "../test/yaml/akri-debug-echo-foo.yaml", - "../test/yaml/akri-udev-video.yaml", - "../test/yaml/akri-opcua.yaml", + "../test/yaml/akri-onvif-video-configuration.yaml", + "../test/yaml/akri-debug-echo-foo-configuration.yaml", + "../test/yaml/akri-udev-video-configuration.yaml", + "../test/yaml/akri-opcua-configuration.yaml", ]; for file in &files { log::trace!("test file: {}", &file); diff --git a/test/run-webhook.md b/test/run-webhook.md index 67b97655c..8a5eaba18 100644 --- a/test/run-webhook.md +++ b/test/run-webhook.md @@ -2,7 +2,7 @@ File: `/tests/run-webhook.py` -Complements existing Python-based end-to-end test [script](/test/run-end-to-end.py) with a script to test Akri configured to use the Configuration Admission Controller Webhook ([README](/webhooks/validating/configuration/README.me)). +Complements existing Python-based end-to-end test [script](/test/run-end-to-end.py) with a script to test Akri configured to use the Configuration Admission Controller Webhook ([README](/webhooks/validating/configuration/README.md)). The Webhook validates Akri Configurations, permitting (semantically) valid Configurations to be applied to a cluster and prohibiting (semantically) invalid Configurations. diff --git a/test/yaml/akri-debug-echo-foo.yaml b/test/yaml/akri-debug-echo-foo-configuration.yaml similarity index 100% rename from test/yaml/akri-debug-echo-foo.yaml rename to test/yaml/akri-debug-echo-foo-configuration.yaml diff --git a/test/yaml/akri-onvif-video.yaml b/test/yaml/akri-onvif-video-configuration.yaml similarity index 100% rename from test/yaml/akri-onvif-video.yaml rename to test/yaml/akri-onvif-video-configuration.yaml diff --git a/test/yaml/akri-opcua.yaml b/test/yaml/akri-opcua-configuration.yaml similarity index 100% rename from test/yaml/akri-opcua.yaml rename to test/yaml/akri-opcua-configuration.yaml diff --git a/test/yaml/akri-udev-video.yaml b/test/yaml/akri-udev-video-configuration.yaml similarity index 100% rename from test/yaml/akri-udev-video.yaml rename to test/yaml/akri-udev-video-configuration.yaml diff --git a/version.txt b/version.txt index b61604874..844f6a91a 100644 --- a/version.txt +++ b/version.txt @@ -1 +1 @@ -0.6.2 +0.6.3 diff --git a/webhooks/validating/configuration/Cargo.toml b/webhooks/validating/configuration/Cargo.toml index 009f92d46..18430ae2c 100644 --- a/webhooks/validating/configuration/Cargo.toml +++ b/webhooks/validating/configuration/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "webhook-configuration" -version = "0.6.2" +version = "0.6.3" authors = ["DazWilkin "] edition = "2018"