From 3b575c781065c08d5a7da8fb694955b9819ba077 Mon Sep 17 00:00:00 2001 From: Vladimir Vagaytsev Date: Wed, 23 Mar 2022 15:08:54 +0100 Subject: [PATCH] chore(release): bump version to 0.12.37 --- CHANGELOG.md | 15 +++++++++++++++ README.md | 2 +- cli/package.json | 2 +- core/package.json | 2 +- dashboard/package.json | 2 +- docs/advanced/terraform.md | 6 +++--- docs/advanced/using-remote-sources.md | 2 +- docs/getting-started/5-configure-your-project.md | 2 +- docs/guides/cloud-provider-setup.md | 2 +- docs/guides/container-modules.md | 4 ++-- docs/guides/remote-kubernetes.md | 2 +- docs/guides/using-garden-in-ci.md | 2 +- docs/guides/using-helm-charts.md | 8 ++++---- docs/misc/faq.md | 10 +++++----- docs/reference/module-types/jib-container.md | 2 +- docs/reference/providers/conftest-kubernetes.md | 2 +- docs/reference/providers/conftest.md | 2 +- docs/reference/providers/hadolint.md | 2 +- docs/reference/providers/jib.md | 2 +- docs/reference/providers/openfaas.md | 2 +- docs/using-garden/module-templates.md | 4 ++-- docs/using-garden/modules.md | 2 +- docs/using-garden/tasks.md | 2 +- docs/using-garden/tests.md | 2 +- e2e/package.json | 2 +- package.json | 2 +- plugins/conftest-container/package.json | 2 +- plugins/conftest-kubernetes/package.json | 2 +- plugins/conftest/package.json | 2 +- plugins/jib/package.json | 2 +- plugins/maven-container/package.json | 2 +- sdk/package.json | 2 +- 32 files changed, 57 insertions(+), 42 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6a1b682880..aa9142992b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,4 +1,19 @@ + +## [0.12.37](https://github.com/garden-io/garden/compare/0.12.36...0.12.37) (2022-03-18) + +### Bug Fixes + +* fix maven download for windows ([7686eade](https://github.com/garden-io/garden/commit/7686eade)) +* **docs:** fix broken anchor link ([9b6f264e](https://github.com/garden-io/garden/commit/9b6f264e)) +* **examples:** updated golang version in examples ([241118e6](https://github.com/garden-io/garden/commit/241118e6)) +* **exec:** properly handle empty lines in local service logs ([5147f60e](https://github.com/garden-io/garden/commit/5147f60e)) +* **k8s:** escape spaces in local mutagen dests ([f100d1d2](https://github.com/garden-io/garden/commit/f100d1d2)) + +### Features + +* **template:** add 'string' template function ([6b96296c](https://github.com/garden-io/garden/commit/6b96296c)) + ## [0.12.36](https://github.com/garden-io/garden/compare/0.12.35...0.12.36) (2022-03-15) diff --git a/README.md b/README.md index 4188606e2e..6e2653aa39 100644 --- a/README.md +++ b/README.md @@ -54,7 +54,7 @@ Users typically implement Garden for one or more of the following: - **Namespaced environments on demand:** Any developer can spin up (and tear down) a namespaced environment in a shared cluster without help from DevOps, or an environment can be created by CI on every pull request. - **Stack-aware builds and testing with result caching:** Garden is aware of the relationships between the services in your stack, and so instead of building an entire application or running a full suite of integration tests every time, Garden will only build or test what’s necessary based on what’s been changed. These build and test results are cached and can be shared across developers on a team. The result: much faster builds and test runs, which means faster feedback loops for developers. - **Shared development clusters with fast in-cluster building:** Build images in your Kubernetes development cluster, thus eliminating the need for local Kubernetes clusters (in other words, no Docker or Kubernetes on your local machine). -- **Define [tasks](https://github.com/garden-io/garden/tree/0.12.36/examples/tasks)** that run as part of your deployment process—e.g. database migrations or scaffolding. +- **Define [tasks](https://github.com/garden-io/garden/tree/0.12.37/examples/tasks)** that run as part of your deployment process—e.g. database migrations or scaffolding. - **[Remote sources (multi-repository) support:](https://docs.garden.io/advanced/using-remote-sources)** Garden allows your project to automatically pull code from different repositories. - **Hardware and platform flexibility:** Run Garden on-prem or in one of several supported cloud providers. Build, test, and deploy Docker containers, [Helm charts](https://docs.garden.io/guides/using-helm-charts), and more. Choose from a variety of Kubernetes platforms and CI tools. - **Terraform integration:** Garden includes a [Terraform provider](https://docs.garden.io/advanced/terraform) that you can use to automatically validate and provision infrastructure as part of your project. diff --git a/cli/package.json b/cli/package.json index 20c54f2f54..fda820795a 100644 --- a/cli/package.json +++ b/cli/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/cli", - "version": "0.12.36", + "version": "0.12.37", "description": "Cloud native testing platform for testing and developing container applications on Kubernetes", "repository": { "type": "git", diff --git a/core/package.json b/core/package.json index 5aa7f05b3d..cec2b7d257 100644 --- a/core/package.json +++ b/core/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/core", - "version": "0.12.36", + "version": "0.12.37", "description": "A full-featured development framework for containers and serverless", "repository": { "type": "git", diff --git a/dashboard/package.json b/dashboard/package.json index 71f7120457..c461177672 100644 --- a/dashboard/package.json +++ b/dashboard/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/dashboard", - "version": "0.12.36", + "version": "0.12.37", "private": true, "devDependencies": { "@garden-io/cli": "*", diff --git a/docs/advanced/terraform.md b/docs/advanced/terraform.md index 404e528746..20a2d2a5a7 100644 --- a/docs/advanced/terraform.md +++ b/docs/advanced/terraform.md @@ -15,7 +15,7 @@ Under the hood, Garden simply wraps Terraform, so there's no magic involved. Gar The `terraform` provider can both provision a Terraform stack when initializing Garden, or through `terraform` modules that are deployed like other services in your stack. -The former, having a single Terraform stack for your whole project, is most helpful if other provider configurations need to reference the outputs from your Terraform stack, or if most/all of your services depend on the infrastructure provisioned in your Terraform stack. A good example of this is the [terraform-gke example](https://github.com/garden-io/garden/tree/0.12.36/examples/terraform-gke) project, which provisions a GKE cluster that the `kubernetes` provider then runs on, along with the services in the project. The drawback is that Garden doesn't currently watch for changes in those Terraform files, and you need to restart to apply new changes, or apply them manually. +The former, having a single Terraform stack for your whole project, is most helpful if other provider configurations need to reference the outputs from your Terraform stack, or if most/all of your services depend on the infrastructure provisioned in your Terraform stack. A good example of this is the [terraform-gke example](https://github.com/garden-io/garden/tree/0.12.37/examples/terraform-gke) project, which provisions a GKE cluster that the `kubernetes` provider then runs on, along with the services in the project. The drawback is that Garden doesn't currently watch for changes in those Terraform files, and you need to restart to apply new changes, or apply them manually. The latter method, using one or more `terraform` _modules_, can be better if your other providers don't need to reference the stack outputs but your _services, tasks and tests_ do. In this style, you can basically create small Terraform stacks that are part of your Stack Graph much like other services. A good example would be deploying a database instance, that other services in your project can then connect to. @@ -34,7 +34,7 @@ providers: ... ``` -If you'd like to apply the stack when starting Garden, and then reference the stack outputs in other providers (or modules), you need to add a couple of more flags. Here's the project config from the aforementioned [terraform-gke example](https://github.com/garden-io/garden/tree/0.12.36/examples/terraform-gke): +If you'd like to apply the stack when starting Garden, and then reference the stack outputs in other providers (or modules), you need to add a couple of more flags. Here's the project config from the aforementioned [terraform-gke example](https://github.com/garden-io/garden/tree/0.12.37/examples/terraform-gke): ```yaml kind: Project @@ -109,6 +109,6 @@ Much like other modules, you can also reference Terraform definitions in other r ## Next steps -Check out the [terraform-gke example](https://github.com/garden-io/garden/tree/0.12.36/examples/terraform-gke) project. Also take a look at the [Terraform provider reference](../reference/providers/terraform.md) and the [Terraform module type reference](../reference/module-types/terraform.md) for details on all the configuration parameters. +Check out the [terraform-gke example](https://github.com/garden-io/garden/tree/0.12.37/examples/terraform-gke) project. Also take a look at the [Terraform provider reference](../reference/providers/terraform.md) and the [Terraform module type reference](../reference/module-types/terraform.md) for details on all the configuration parameters. If you're having issues with Terraform itself, please refer to the [official docs](https://www.terraform.io/docs/index.html). diff --git a/docs/advanced/using-remote-sources.md b/docs/advanced/using-remote-sources.md index ce3f2a782f..24074b1747 100644 --- a/docs/advanced/using-remote-sources.md +++ b/docs/advanced/using-remote-sources.md @@ -11,7 +11,7 @@ You can import **two** types of remote repositories with Garden: > **Remote _module_**: The source code for a single Garden module. In this case, the `garden.yml` config file is stored in the main project repository while the module code itself is in the remote repository. -The code examples below are from our [remote sources example](https://github.com/garden-io/garden/tree/0.12.36/examples/remote-sources). +The code examples below are from our [remote sources example](https://github.com/garden-io/garden/tree/0.12.37/examples/remote-sources). ## Importing Remote Repositories diff --git a/docs/getting-started/5-configure-your-project.md b/docs/getting-started/5-configure-your-project.md index a4c089c1ec..1059dc100f 100644 --- a/docs/getting-started/5-configure-your-project.md +++ b/docs/getting-started/5-configure-your-project.md @@ -6,7 +6,7 @@ Garden is a powerful and flexible tool, and there are several things to learn al 1. Place the project configuration you created for the example, which will be all set to connect to your cluster, in your own project root. 2. Go through the [Using Garden](../using-garden/README.md) documentation section. This will cover all the key concepts, and introduce all the moving parts, including the different module types that Garden supports. -3. Have a look at the [examples](https://github.com/garden-io/garden/tree/0.12.36/examples) folder in the Garden repository, which offers several usage examples that you can refer to while building out your project. +3. Have a look at the [examples](https://github.com/garden-io/garden/tree/0.12.37/examples) folder in the Garden repository, which offers several usage examples that you can refer to while building out your project. 4. Set up your modules, getting them building and deploying, **one at a time**. 5. Make sure your whole project builds and deploys successfully. 6. Start thinking about tests. Garden excels at managing all the different test suites in your stack, especially integration and end-to-end tests that need to run inside your deployment environment. diff --git a/docs/guides/cloud-provider-setup.md b/docs/guides/cloud-provider-setup.md index c5c986af3d..3b657a22b1 100644 --- a/docs/guides/cloud-provider-setup.md +++ b/docs/guides/cloud-provider-setup.md @@ -52,7 +52,7 @@ Run `garden --env=remote plugins kubernetes cluster-init`, then `garden dev --en ### Optional: Use in-cluster building with GCR and Kaniko -Take a look at the [gke example project](https://github.com/garden-io/garden/tree/0.12.36/examples/gke)) to see the additional steps required to set up in-cluster building on GKE with Kaniko and GCR as a deployment registry. +Take a look at the [gke example project](https://github.com/garden-io/garden/tree/0.12.37/examples/gke)) to see the additional steps required to set up in-cluster building on GKE with Kaniko and GCR as a deployment registry. ### Optional: Configure DNS diff --git a/docs/guides/container-modules.md b/docs/guides/container-modules.md index ab3c2b86bd..c80c52180c 100644 --- a/docs/guides/container-modules.md +++ b/docs/guides/container-modules.md @@ -93,7 +93,7 @@ Generally, you can use any template strings available for module configs for the In the case of Kubernetes, Garden will take the simplified `container` service specification and convert it to the corresponding Kubernetes manifests, i.e. Deployment, Service and (if applicable) Ingress resources. -Here, for example, is the spec for the `frontend` service in our example [demo project](https://github.com/garden-io/garden/tree/0.12.36/examples/demo-project): +Here, for example, is the spec for the `frontend` service in our example [demo project](https://github.com/garden-io/garden/tree/0.12.37/examples/demo-project): ```yaml kind: Module @@ -177,7 +177,7 @@ kubectl --namespace create secret generic --from-literal=some Where `` is your project namespace (which is either set with `namespace` in your provider config, or defaults to your project name). There are notably other, more secure ways to create secrets via `kubectl`. Please refer to the official [Kubernetes Secrets docs](https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-using-kubectl-create-secret) for details. -Also check out the [Kubernetes Secrets example project](https://github.com/garden-io/garden/tree/0.12.36/examples/kubernetes-secrets) for a working example. +Also check out the [Kubernetes Secrets example project](https://github.com/garden-io/garden/tree/0.12.37/examples/kubernetes-secrets) for a working example. ## Running tests diff --git a/docs/guides/remote-kubernetes.md b/docs/guides/remote-kubernetes.md index 5bd6210b9f..36648382b3 100644 --- a/docs/guides/remote-kubernetes.md +++ b/docs/guides/remote-kubernetes.md @@ -131,7 +131,7 @@ to your registry's documentation on how to do that (for Docker Hub you simply ru ### Ingress, TLS and DNS -By default, Garden will not install an ingress controller for remote environments. This can be toggled by setting the [`setupIngressController` flag](../reference/providers/kubernetes.md#providerssetupingresscontroller) to `nginx`. Alternatively, you can set up your own ingress controller, e.g. using [Traefik](https://traefik.io/), [Ambassador](https://www.getambassador.io/) or [Istio](https://istio.io/). You can find examples for [using Garden with Ambassador](https://github.com/garden-io/garden/tree/0.12.36/examples/ambassador) and [with Istio](https://github.com/garden-io/garden/tree/0.12.36/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.12.36/examples). +By default, Garden will not install an ingress controller for remote environments. This can be toggled by setting the [`setupIngressController` flag](../reference/providers/kubernetes.md#providerssetupingresscontroller) to `nginx`. Alternatively, you can set up your own ingress controller, e.g. using [Traefik](https://traefik.io/), [Ambassador](https://www.getambassador.io/) or [Istio](https://istio.io/). You can find examples for [using Garden with Ambassador](https://github.com/garden-io/garden/tree/0.12.37/examples/ambassador) and [with Istio](https://github.com/garden-io/garden/tree/0.12.37/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.12.37/examples). You'll also need to point one or more DNS entries to your cluster, and configure a TLS certificate for the hostnames you will expose for ingress. diff --git a/docs/guides/using-garden-in-ci.md b/docs/guides/using-garden-in-ci.md index d89b1cd392..d00c4bc212 100644 --- a/docs/guides/using-garden-in-ci.md +++ b/docs/guides/using-garden-in-ci.md @@ -23,7 +23,7 @@ The guide is based on the [Remote Kubernetes](https://docs.garden.io/guides/remo ## Project overview -The project is based on our basic [demo-project](https://github.com/garden-io/garden/tree/0.12.36/examples/demo-project) example, but configured for multiple environments. Additionally it contains a CircleCI config file. You'll find the entire source code [here](https://github.com/garden-io/ci-demo-project). +The project is based on our basic [demo-project](https://github.com/garden-io/garden/tree/0.12.37/examples/demo-project) example, but configured for multiple environments. Additionally it contains a CircleCI config file. You'll find the entire source code [here](https://github.com/garden-io/ci-demo-project). The CI pipeline is configured so that Garden tests the project and deploys it to a **preview** environment on every pull request. Additionally, it tests the project and deploys it to a separate **staging** environment on every merge to the `master` branch. diff --git a/docs/guides/using-helm-charts.md b/docs/guides/using-helm-charts.md index bccebe2901..e25db1a01f 100644 --- a/docs/guides/using-helm-charts.md +++ b/docs/guides/using-helm-charts.md @@ -2,13 +2,13 @@ The [Helm](https://helm.sh/) package manager is one of the most commonly used tools for managing Kubernetes manifests. Garden supports using your own Helm charts, alongside your container modules, via the `kubernetes` and `local-kubernetes` providers. This guide shows you how to configure and use 3rd-party (or otherwise external) Helm charts, as well as your own charts in your Garden project. We also go through how to set up tests, tasks and hot-reloading for your charts. -In this guide we'll be using the [vote-helm](https://github.com/garden-io/garden/tree/0.12.36/examples/vote-helm) project. If you prefer to just check out a complete example, the project itself is also a good resource. +In this guide we'll be using the [vote-helm](https://github.com/garden-io/garden/tree/0.12.37/examples/vote-helm) project. If you prefer to just check out a complete example, the project itself is also a good resource. You may also want to check out the full [helm module reference](../reference/module-types/helm.md). _Note: If you only need a way to deploy some Kubernetes manifests and don't need all the features of Helm, you can_ _use the simpler `kubernetes` module type instead. Check out the_ -_[kubernetes-module](https://github.com/garden-io/garden/tree/0.12.36/examples/kubernetes-module) example for more info._ +_[kubernetes-module](https://github.com/garden-io/garden/tree/0.12.37/examples/kubernetes-module) example for more info._ ## Basics @@ -304,7 +304,7 @@ You can define a remote environment as a `production` environment by setting the ## Next steps -Check out the full [helm module reference](../reference/module-types/helm.md) for more details, and the [vote-helm](https://github.com/garden-io/garden/tree/0.12.36/examples/vote-helm) example project for a full project that showcases Garden's Helm support. +Check out the full [helm module reference](../reference/module-types/helm.md) for more details, and the [vote-helm](https://github.com/garden-io/garden/tree/0.12.37/examples/vote-helm) example project for a full project that showcases Garden's Helm support. -Also check out the [kubernetes-module](https://github.com/garden-io/garden/tree/0.12.36/examples/kubernetes-module) +Also check out the [kubernetes-module](https://github.com/garden-io/garden/tree/0.12.37/examples/kubernetes-module) example for a simpler alternative, if you don't need all the features of Helm. diff --git a/docs/misc/faq.md b/docs/misc/faq.md index 0cf7c94f3e..3b0dd3c0ad 100644 --- a/docs/misc/faq.md +++ b/docs/misc/faq.md @@ -45,7 +45,7 @@ You can also deploy `kubernetes` and `helm` modules to their own namespaces. ### How do I share code between modules? -You can use the [copy directive](https://docs.garden.io/reference/module-types/container#build-dependencies-copy) of the `build.dependencies[]` field for that. See e.g. [this example project](https://github.com/garden-io/garden/tree/0.12.36/examples/build-dependencies). +You can use the [copy directive](https://docs.garden.io/reference/module-types/container#build-dependencies-copy) of the `build.dependencies[]` field for that. See e.g. [this example project](https://github.com/garden-io/garden/tree/0.12.37/examples/build-dependencies). Alternatively you can hoist your `garden.yml` file so that it is at the same level or parent to all relevant build context and use the `include` field. @@ -65,7 +65,7 @@ Use the [`targetImage` field](https://docs.garden.io/reference/module-types/cont ### How do I use base images? -See [this example project](https://github.com/garden-io/garden/tree/0.12.36/examples/base-image). +See [this example project](https://github.com/garden-io/garden/tree/0.12.37/examples/base-image). ### Can I use runtime variables in container builds (e.g. from tasks)? @@ -112,11 +112,11 @@ include: [frontend/**/*] Note that you can put multiple Garden configuration files in the same directory, e.g. `project.garden.yml`, `api.garden.yml` and `frontend.garden.yml`. -If you need the Dockerfile outside of the module root because you want to share it with other modules, you should consider having a single base image instead and then let each module have its own Dockerfile that's built on the base image. See the [base image example project](https://github.com/garden-io/garden/tree/0.12.36/examples/base-image) for an example of this. +If you need the Dockerfile outside of the module root because you want to share it with other modules, you should consider having a single base image instead and then let each module have its own Dockerfile that's built on the base image. See the [base image example project](https://github.com/garden-io/garden/tree/0.12.37/examples/base-image) for an example of this. ### How do I include files/dirs (e.g. shared libraries) from outside the module root with the build context? -See [this example project](https://github.com/garden-io/garden/tree/0.12.36/examples/build-dependencies). +See [this example project](https://github.com/garden-io/garden/tree/0.12.37/examples/build-dependencies). ### How do I add Docker specific flags to the build command? @@ -130,7 +130,7 @@ You can use the `dockerfile` field. For example: dockerfile: "${environment.name == 'prod' ? Dockerfile.prod : Dockerfile.dev}" ``` -See also the [base image example project](https://github.com/garden-io/garden/tree/0.12.36/examples/base-image) for an example of this. +See also the [base image example project](https://github.com/garden-io/garden/tree/0.12.37/examples/base-image) for an example of this. ## Remote Building diff --git a/docs/reference/module-types/jib-container.md b/docs/reference/module-types/jib-container.md index 22c6070df4..becf880972 100644 --- a/docs/reference/module-types/jib-container.md +++ b/docs/reference/module-types/jib-container.md @@ -7,7 +7,7 @@ tocTitle: "`jib-container`" ## Description -Extends the [container module type](./container.md) to build the image with [Jib](https://github.com/GoogleContainerTools/jib). Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.12.36/examples/jib-container) to see it in action. +Extends the [container module type](./container.md) to build the image with [Jib](https://github.com/GoogleContainerTools/jib). Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.12.37/examples/jib-container) to see it in action. The image is always built locally, directly from the module source directory (see the note on that below), before shipping the container image to the right place. You can set `build.tarOnly: true` to only build the image as a tarball. diff --git a/docs/reference/providers/conftest-kubernetes.md b/docs/reference/providers/conftest-kubernetes.md index ea3001d717..26c6ac167b 100644 --- a/docs/reference/providers/conftest-kubernetes.md +++ b/docs/reference/providers/conftest-kubernetes.md @@ -14,7 +14,7 @@ Simply add this provider to your project configuration, and configure your polic reference for how to configure default policies, default namespaces, and test failure thresholds for the generated modules. -See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.36/examples/conftest) for a simple +See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.37/examples/conftest) for a simple usage example. Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our [configuration guide](../../using-garden/configuration-overview.md). diff --git a/docs/reference/providers/conftest.md b/docs/reference/providers/conftest.md index ef27987dbb..4b4288deb8 100644 --- a/docs/reference/providers/conftest.md +++ b/docs/reference/providers/conftest.md @@ -9,7 +9,7 @@ tocTitle: "`conftest`" This provider allows you to validate your configuration files against policies that you specify, using the [conftest tool](https://github.com/instrumenta/conftest) and Open Policy Agent rego query files. The provider creates a module type of the same name, which allows you to specify files to validate. Each module then creates a Garden test that becomes part of your Stack Graph. -Note that, in many cases, you'll actually want to use more specific providers that can automatically configure your `conftest` modules, e.g. the [`conftest-container`](../module-types/conftest.md) and/or [`conftest-kubernetes`](../module-types/conftest.md) providers. See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.36/examples/conftest) for a simple usage example of the latter. +Note that, in many cases, you'll actually want to use more specific providers that can automatically configure your `conftest` modules, e.g. the [`conftest-container`](../module-types/conftest.md) and/or [`conftest-kubernetes`](../module-types/conftest.md) providers. See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.37/examples/conftest) for a simple usage example of the latter. If those don't match your needs, you can use this provider directly and manually configure your `conftest` modules. Simply add this provider to your project configuration, and see the [conftest module documentation](../module-types/conftest.md) for a detailed reference. Also, check out the below reference for how to configure default policies, default namespaces, and test failure thresholds for all `conftest` modules. diff --git a/docs/reference/providers/hadolint.md b/docs/reference/providers/hadolint.md index 16a6d173c8..94e621987a 100644 --- a/docs/reference/providers/hadolint.md +++ b/docs/reference/providers/hadolint.md @@ -11,7 +11,7 @@ This provider creates a [`hadolint`](../module-types/hadolint.md) module type, a To configure `hadolint`, you can use `.hadolint.yaml` config files. For each test, we first look for one in the relevant module root. If none is found there, we check the project root, and if none is there we fall back to default configuration. Note that for reasons of portability, we do not fall back to global/user configuration files. -See the [hadolint docs](https://github.com/hadolint/hadolint#configure) for details on how to configure it, and the [hadolint example project](https://github.com/garden-io/garden/tree/0.12.36/examples/hadolint) for a usage example. +See the [hadolint docs](https://github.com/hadolint/hadolint#configure) for details on how to configure it, and the [hadolint example project](https://github.com/garden-io/garden/tree/0.12.37/examples/hadolint) for a usage example. Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our [configuration guide](../../using-garden/configuration-overview.md). diff --git a/docs/reference/providers/jib.md b/docs/reference/providers/jib.md index 308850e23f..2bb9102aed 100644 --- a/docs/reference/providers/jib.md +++ b/docs/reference/providers/jib.md @@ -11,7 +11,7 @@ tocTitle: "`jib`" Provides support for [Jib](https://github.com/GoogleContainerTools/jib) via the [jib module type](../module-types/jib-container.md). -Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.12.36/examples/jib-container) to see it in action. +Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.12.37/examples/jib-container) to see it in action. Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our [configuration guide](../../using-garden/configuration-overview.md). diff --git a/docs/reference/providers/openfaas.md b/docs/reference/providers/openfaas.md index 80346ff911..ad716b06c3 100644 --- a/docs/reference/providers/openfaas.md +++ b/docs/reference/providers/openfaas.md @@ -11,7 +11,7 @@ This provider adds support for [OpenFaaS](https://www.openfaas.com/). It adds th See the reference below for configuration options for `faas-netes`, and the [module type docs](../module-types/openfaas.md) for how to configure the individual functions. -Also see the [openfaas example project](https://github.com/garden-io/garden/tree/0.12.36/examples/openfaas) for a simple usage example. +Also see the [openfaas example project](https://github.com/garden-io/garden/tree/0.12.37/examples/openfaas) for a simple usage example. Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our [configuration guide](../../using-garden/configuration-overview.md). diff --git a/docs/using-garden/module-templates.md b/docs/using-garden/module-templates.md index dc4818f48b..9036137800 100644 --- a/docs/using-garden/module-templates.md +++ b/docs/using-garden/module-templates.md @@ -17,7 +17,7 @@ This feature was introduced in Garden 0.12.7. Please make sure you have an up-to ## How it works -We'll use the [`templated-k8s-container example`](https://github.com/garden-io/garden/tree/0.12.36/examples/templated-k8s-container) to illustrate how module templates work. This example has a `k8s-container` template, that generates one `container` module for building an image, and one `kubernetes` module for deploying that image. A template like this is useful to customize the Kubernetes manifests for your services, but of course it's just one simple example of what you could do. +We'll use the [`templated-k8s-container example`](https://github.com/garden-io/garden/tree/0.12.37/examples/templated-k8s-container) to illustrate how module templates work. This example has a `k8s-container` template, that generates one `container` module for building an image, and one `kubernetes` module for deploying that image. A template like this is useful to customize the Kubernetes manifests for your services, but of course it's just one simple example of what you could do. The template is defined like this: @@ -158,7 +158,7 @@ Garden will then scan that repo when starting up, and you can reference the temp - [ModuleTemplate reference docs](../reference/module-template-config.md). - [`templated` module type reference docs](../reference/module-types/templated.md). -- [`templated-k8s-container example`](https://github.com/garden-io/garden/tree/0.12.36/examples/templated-k8s-container). +- [`templated-k8s-container example`](https://github.com/garden-io/garden/tree/0.12.37/examples/templated-k8s-container). ## Next steps diff --git a/docs/using-garden/modules.md b/docs/using-garden/modules.md index b5e5bfdb42..5328510abc 100644 --- a/docs/using-garden/modules.md +++ b/docs/using-garden/modules.md @@ -9,7 +9,7 @@ Modules are the basic **unit of building** in Garden. They are usually the first A module can correspond to a Dockerfile and its associated code, a remote Docker image, a Helm chart, an OpenFaaS function, and more, all depending on the module type. -Below is a simple example of a module's `garden.yml` (from the [`demo-project`](https://github.com/garden-io/garden/tree/0.12.36/examples/demo-project) example project): +Below is a simple example of a module's `garden.yml` (from the [`demo-project`](https://github.com/garden-io/garden/tree/0.12.37/examples/demo-project) example project): ```yaml kind: Module diff --git a/docs/using-garden/tasks.md b/docs/using-garden/tasks.md index 9be93b5097..d101a1cc56 100644 --- a/docs/using-garden/tasks.md +++ b/docs/using-garden/tasks.md @@ -86,7 +86,7 @@ tasks: - postgres ``` -The full example is [available here](https://github.com/garden-io/garden/tree/0.12.36/examples/vote-helm/postgres/garden.yml). There's [also a version](https://github.com/garden-io/garden/tree/0.12.36/examples/vote) that uses the `container` module type instead of Helm charts. +The full example is [available here](https://github.com/garden-io/garden/tree/0.12.37/examples/vote-helm/postgres/garden.yml). There's [also a version](https://github.com/garden-io/garden/tree/0.12.37/examples/vote) that uses the `container` module type instead of Helm charts. ## Advanced diff --git a/docs/using-garden/tests.md b/docs/using-garden/tests.md index fb933e64d1..0752ebbe5b 100644 --- a/docs/using-garden/tests.md +++ b/docs/using-garden/tests.md @@ -49,7 +49,7 @@ For full test configuration by module type, please take a look at our [reference ### Integration Testing -Below is an example of a `frontend` module that has a `unit` test and an `integ` test that depends on a `backend` module. The `integ` test checks whether the frontend gets the correct response from the backend. The example is based on our [vote example project](https://github.com/garden-io/garden/tree/0.12.36/examples/vote). +Below is an example of a `frontend` module that has a `unit` test and an `integ` test that depends on a `backend` module. The `integ` test checks whether the frontend gets the correct response from the backend. The example is based on our [vote example project](https://github.com/garden-io/garden/tree/0.12.37/examples/vote). Here's the configuration for `frontend` module: diff --git a/e2e/package.json b/e2e/package.json index ed03fb5ac1..ab3cd680e9 100644 --- a/e2e/package.json +++ b/e2e/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/e2e", - "version": "0.12.36", + "version": "0.12.37", "description": "End-to-end tests for the Garden CLI", "repository": { "type": "git", diff --git a/package.json b/package.json index 7f7d14c98d..a79d3efbbc 100644 --- a/package.json +++ b/package.json @@ -5,7 +5,7 @@ "type": "git", "url": "git+https://github.com/garden-io/garden.git" }, - "version": "0.12.36", + "version": "0.12.37", "author": "Garden Technologies, Inc. ", "license": "MPL-2.0", "homepage": "https://github.com/garden-io/garden", diff --git a/plugins/conftest-container/package.json b/plugins/conftest-container/package.json index eb6e120820..c679b9e066 100644 --- a/plugins/conftest-container/package.json +++ b/plugins/conftest-container/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/garden-conftest-container", - "version": "0.12.36", + "version": "0.12.37", "description": "Auto-generator for the conftest plugin and Garden container modules", "main": "index.js", "dependencies": { diff --git a/plugins/conftest-kubernetes/package.json b/plugins/conftest-kubernetes/package.json index c43eda91ba..cd959016b1 100644 --- a/plugins/conftest-kubernetes/package.json +++ b/plugins/conftest-kubernetes/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/garden-conftest-kubernetes", - "version": "0.12.36", + "version": "0.12.37", "description": "Auto-generator for the conftest plugin and Garden kubernetes/helm modules", "main": "index.js", "private": true, diff --git a/plugins/conftest/package.json b/plugins/conftest/package.json index 2ca3031d75..829da97baa 100644 --- a/plugins/conftest/package.json +++ b/plugins/conftest/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/garden-conftest", - "version": "0.12.36", + "version": "0.12.37", "description": "conftest plugin for Garden", "main": "index.js", "private": true, diff --git a/plugins/jib/package.json b/plugins/jib/package.json index 5daba31549..18d8166ed2 100644 --- a/plugins/jib/package.json +++ b/plugins/jib/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/garden-jib", - "version": "0.12.36", + "version": "0.12.37", "description": "Jib container plugin for Garden", "main": "index.js", "dependencies": { diff --git a/plugins/maven-container/package.json b/plugins/maven-container/package.json index 37e2eb305b..8ee21931c1 100644 --- a/plugins/maven-container/package.json +++ b/plugins/maven-container/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/garden-maven-container", - "version": "0.12.36", + "version": "0.12.37", "description": "maven-container plugin for Garden (DEPRECATED)", "main": "index.js", "dependencies": { diff --git a/sdk/package.json b/sdk/package.json index 579e6333fd..b33641cbc1 100644 --- a/sdk/package.json +++ b/sdk/package.json @@ -1,6 +1,6 @@ { "name": "@garden-io/sdk", - "version": "0.12.36", + "version": "0.12.37", "description": "TypeScript plugin SDK for Garden", "repository": { "type": "git",