You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by he...@apache.org on 2022/09/15 13:03:16 UTC

[brooklyn-docs] branch master updated: fix reference to container sensor

This is an automated email from the ASF dual-hosted git repository.

heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new eb126e1a fix reference to container sensor
eb126e1a is described below

commit eb126e1a5b82c199811195fbab6e0160298d6392
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Thu Sep 15 14:03:02 2022 +0100

    fix reference to container sensor
---
 guide/blueprints/yaml-reference.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guide/blueprints/yaml-reference.md b/guide/blueprints/yaml-reference.md
index d764f085..4b04be59 100644
--- a/guide/blueprints/yaml-reference.md
+++ b/guide/blueprints/yaml-reference.md
@@ -56,7 +56,7 @@ the entity being defined, with these being the most common:
     to define an effector with the given name implemented by the given SSH command
     (on an entity which as an ssh-able machine)
 
-  * `org.apache.brooklyn.core.sensor.ssh.SshCommandSensor`: takes a `name` and `command`,
+  * `org.apache.brooklyn.tasks.kubectl.ContainerSensor`: takes a `name` and `command`,
     and optionally a `period` (e.g. `1h`) or `triggers` (a sensor name, or list containing sensor names or
     maps of the form `{entity: id, sensor: name}`), to create a sensor feed which populates the sensor with
     the given name by running the given command (on an entity which as an ssh-able machine);