You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/09/14 11:27:50 UTC

[camel-k] branch master updated: Document Update (#1704)

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

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/master by this push:
     new 29d29fe  Document Update (#1704)
29d29fe is described below

commit 29d29fefd835a0b32e1ec0ba7c74e2470b174d8b
Author: Nitesh Koushik S <39...@users.noreply.github.com>
AuthorDate: Mon Sep 14 16:56:54 2020 +0530

    Document Update (#1704)
    
    Changes made from interation to "iteration"
---
 docs/modules/ROOT/pages/architecture/operator.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/architecture/operator.adoc b/docs/modules/ROOT/pages/architecture/operator.adoc
index 541edb4..f9a3fb4 100644
--- a/docs/modules/ROOT/pages/architecture/operator.adoc
+++ b/docs/modules/ROOT/pages/architecture/operator.adoc
@@ -41,7 +41,7 @@ type Action interface {
 }
 ----
 <1> Determine if the action can handle the CR as example by looking at the phase of the CR which is store as part of the status sub resource.
-<2> Implement the action and return a non `nil` instance to signal to the controller that the CR need to be updated with the new one, instead if the method returns a `nil` instance, then nothing will happen and unless the CR changes outside the control of the operator, the same action will be invoked on the next interation. This is useful when a CR need to delegate some work to a different controller so the CR won't be moved to the next stage till the sub operation has completed. 
+<2> Implement the action and return a non `nil` instance to signal to the controller that the CR need to be updated with the new one, instead if the method returns a `nil` instance, then nothing will happen and unless the CR changes outside the control of the operator, the same action will be invoked on the next iteration. This is useful when a CR need to delegate some work to a different controller so the CR won't be moved to the next stage till the sub operation has completed. 
 
 [NOTE]
 ====