You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/docs/helm/deployments.mdx
+7-1
Original file line number
Diff line number
Diff line change
@@ -341,7 +341,7 @@ Continuing with the example in the previous section, we can deploy it into Kuber
341
341
3. Post-process the Kubernetes manifests generated by Helm by replacing all references to first-party Docker images by their real final registry destination.
342
342
4. Initiate the deployment of the final Kubernetes resources resulting from the post-processing.
343
343
344
-
The `experimental-deploy` goal also supports default Helm pass-through arguments that allow to change the deployment behaviour to be either atomic or a dry-run or even what is the Kubernetes config file (the `kubeconfig` file) and target context to be used in the deployment.
344
+
The `experimental-deploy` goal also supports default Helm pass-through arguments that allow to change the deployment behaviour to be atomic or even what is the Kubernetes config file (the `kubeconfig` file) and target context to be used in the deployment.
345
345
346
346
Please note that the list of valid pass-through arguments has been limited to those that do not alter the reproducibility of the deployment (i.e. `--create-namespace` is not a valid pass-through argument). Those arguments will have equivalent fields in the `helm_deployment` target.
347
347
@@ -351,6 +351,12 @@ For example, to make an atomic deployment into a non-default Kubernetes context
:::note How does Pants authenticate with the Kubernetes cluster?
355
361
Short answer is: it doesn't.
356
362
Pants will invoke Helm under the hood with the appropriate arguments to only perform the deployment. Any authentication steps that may be needed to perform the given deployment have to be done before invoking the `experimental-deploy` goal. If you are planning to run the deployment procedure from your CI/CD pipelines, ensure that all necessary preliminary steps (including authentication with the cluster) are done before the one that triggers the deployment.
Copy file name to clipboardexpand all lines: docs/docs/python/overview/linters-and-formatters.mdx
+14-13
Original file line number
Diff line number
Diff line change
@@ -26,19 +26,20 @@ Pants does several things to speed up running formatters and linters:
26
26
27
27
Linter/formatter support is implemented in separate [backends](../../using-pants/key-concepts/backends.mdx) so that they are easy to opt in to individually:
|`pants.backend.python.lint.pyupgrade`|[Pyupgrade](https://github.com/asottile/pyupgrade): automatically update code to use modern Python idioms like `f-strings`|
41
-
|`pants.backend.experimental.python.lint.ruff`|[Ruff](https://beta.ruff.rs/docs/): an extremely fast Python linter, written in Rust. |
|`pants.backend.python.lint.pyupgrade`|[Pyupgrade](https://github.com/asottile/pyupgrade): automatically update code to use modern Python idioms like `f-strings`|
41
+
|`pants.backend.experimental.python.lint.ruff.check`|[Ruff (for linting)](https://docs.astral.sh/ruff/linter/): an extremely fast Python linter, written in Rust. |
42
+
|`pants.backend.experimental.python.lint.ruff.format`|[Ruff (for formatting)](https://docs.astral.sh/ruff/formatter/): an extremely fast Python code formatter, written in Rust. |
42
43
43
44
To enable, add the appropriate backends in `pants.toml`:
Copy file name to clipboardexpand all lines: docs/docs/python/overview/pex.mdx
+4-2
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,8 @@ In these cases you can override the default shebang using the [`shebang`](../../
87
87
88
88
Pants makes use of the [Pex](https://github.com/pex-tool/pex) command-line tool internally for building PEXes. The Pex version that Pants uses is specified by the `version` option under the `pex-cli` subsystem. The known Pex versions are specified by the `known_versions` option under the `pex-cli` subsystem. You can see all Pex tool options and their current values by running `pants help-advanced pex-cli`. To upgrade the Pex version, update these option values accordingly. For instance, in `pants.toml`, to upgrade to Pex 2.1.143:
@@ -101,6 +102,7 @@ The Pex version determines which Pip versions are supported. To see the lists of
101
102
102
103
The Pip version that Pex uses is determined by the `pip_version` option in Pants. To upgrade the Pip version, update this option value accordingly. For instance, in `pants.toml`, to set the Pip version to be the latest supported by Pex:
You can set auto approve by adding `-auto-approve` to the `[download-terraform].args` setting in `pants.toml`. You can also set it for a single pants invocation with `--download-terraform-args='-auto-approve'`, for example `pants experimental-deploy "--download-terraform-args='-auto-approve'"`.
178
+
179
+
To run `terraform plan`, use the `--dry-run` flag of the `experimental-deploy` goal.
Copy file name to clipboardexpand all lines: docs/docs/using-pants/key-concepts/backends.mdx
+2-1
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,8 @@ The list of all backends (both stable and experimental) is also available via `p
98
98
|`pants.backend.experimental.python.framework.django`| Enables better support for projects using Django: [https://www.djangoproject.com](https://www.djangoproject.com)||
99
99
|`pants.backend.experimental.python.framework.stevedore`| Enables better support for projects using stevedore: [https://docs.openstack.org/stevedore/](https://docs.openstack.org/stevedore/)||
100
100
|`pants.backend.experimental.python.lint.add_trailing_comma`| Enables add-trailing-comma, a Python code formatter: [https://github.com/asottile/add-trailing-comma](https://github.com/asottile/add-trailing-comma)|[`add-trailing-comma`](../../../reference/subsystems/add-trailing-comma.mdx)|
101
-
|`pants.backend.experimental.python.lint.ruff`| Enables Ruff, an extremely fast Python linter: [https://beta.ruff.rs/docs/](https://beta.ruff.rs/docs/)|[Linters and formatters](../../python/overview/linters-and-formatters.mdx)|
101
+
|`pants.backend.experimental.python.lint.ruff.check`| Enables Ruff (for `lint`), an extremely fast Python linter: [https://docs.astral.sh/ruff/linter/](https://docs.astral.sh/ruff/linter/)|[Linters and formatters](../../python/overview/linters-and-formatters.mdx)|
102
+
|`pants.backend.experimental.python.lint.ruff.format`| Enables Ruff (for `fmt`), an extremely fast Python code formatter: [https://docs.astral.sh/ruff/formatter/](https://docs.astral.sh/ruff/formatter/)|[Linters and formatters](../../python/overview/linters-and-formatters.mdx)|
|`pants.backend.experimental.python.typecheck.pyright`| Enables Pyright, a Python type checker: [https://github.com/microsoft/pyright](https://github.com/microsoft/pyright)||
104
105
|`pants.backend.experimental.python.typecheck.pytype`| Enables Pytype, a Python type checker: [https://google.github.io/pytype/](https://google.github.io/pytype/)||
0 commit comments