docs, remove docker CLI, name CL nodes consistently

Author: skudasov

book/src/framework/getting_started.md

@@ -23,10 +23,7 @@ Create an `.envrc` file and put common parameters there (you can use [direnv](ht
 ```
 export CTF_LOG_LEVEL=info
 export CTF_LOKI_STREAM=true
-export LOKI_TENANT_ID=promtail
-export LOKI_URL=http://host.docker.internal:3030/loki/api/v1/push
 export TESTCONTAINERS_RYUK_DISABLED=true
-export RESTY_DEBUG=false
 
 export CTF_CONFIGS=smoke.toml
 export PRIVATE_KEY="ac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80"

book/src/framework/overview.md

@@ -1,11 +1,10 @@
-## Chainlink Testing Framework Harness
+## Framework
 
-This module includes the CTFv2 harness, a lightweight, modular, and data-driven framework designed for combining off-chain and on-chain components while implementing best practices for end-to-end system-level testing:
+The Framework module a lightweight, modular, and data-driven framework designed for combining off-chain and on-chain components while implementing best practices for end-to-end system-level testing:
 
-- **Non-nil configuration**: All test variables must have defaults, automatic validation.
-- **Component isolation**: Components are decoupled via input/output structs, without exposing internal details.
 - **Modular configuration**: No arcane knowledge of framework settings is required; the config is simply a reflection of the components being used in the test. Components declare their own configuration—'what you see is what you get.'
+- **Component isolation**: Components are decoupled via input/output structs, without exposing internal details.
 - **Replaceability and extensibility**: Since components are decoupled via outputs, any deployment component can be swapped with a real service without altering the test code.
-- **Caching**: any component can use cached configs to skip environment setup for faster test development
-- **Integrated observability stack**: use `ctf obs up` to spin up a local observability stack.
+- **Caching**: any component can use cached configs to skip setup for faster test development.
+- **Integrated observability stack**: get all the info you need to develop end-to-end tests: metrics, logs, traces, profiles.
 

book/src/overview.md

@@ -1,4 +1,10 @@
 # Intro
 
 
-The Chainlink Testing Framework (CTF) is a blockchain development framework written in Go. Its primary purpose is to help chainlink developers create extensive integration, e2e, performance, and chaos tests to ensure the stability of the chainlink project. It can also be helpful to those who just want to use chainlink oracles in their projects to help test their contracts, or even for those that aren't using chainlink.
+The Chainlink Testing Framework (CTF) is a blockchain development framework written in Go. 
+Its primary purpose is to help chainlink developers create extensive integration, e2e, performance, and chaos tests to ensure the stability of the chainlink project. 
+It can also be helpful to those who just want to use chainlink oracles in their projects to help test their contracts, or even for those that aren't using chainlink.
+
+[Repository](https://github.com/smartcontractkit/chainlink-testing-framework) contains two major pieces:
+- [Framework](framework/overview.md)
+- [Libraries](libraries.md)

framework/cmd/main.go

@@ -2,7 +2,6 @@ package main
 
 import (
 	"embed"
-	"errors"
 	"fmt"
 	"github.com/pelletier/go-toml"
 	"github.com/rs/zerolog"
@@ -53,7 +52,7 @@ func main() {
 				Usage:   "Control docker containers marked with 'framework=ctf' label",
 				Subcommands: []*cli.Command{
 					{
-						Name:    "clean",
+						Name:    "remove",
 						Aliases: []string{"rm"},
 						Usage:   "Remove Docker containers and networks with 'framework=ctf' label",
 						Action: func(c *cli.Context) error {
@@ -64,48 +63,6 @@ func main() {
 							return nil
 						},
 					},
-					{
-						Name:    "build",
-						Aliases: []string{"c"},
-						Flags: []cli.Flag{
-							&cli.StringFlag{
-								Name:    "dockerfile",
-								Aliases: []string{"f"},
-								Usage:   "Path to the Dockerfile",
-							},
-							&cli.StringFlag{
-								Name:    "context",
-								Aliases: []string{"c"},
-								Usage:   "Build context for the Docker image",
-							},
-							&cli.StringFlag{
-								Name:    "image_name",
-								Aliases: []string{"n"},
-								Usage:   "Image name",
-							},
-						},
-						Usage: "Builds you image and pushes it to a local registry",
-						UsageText: `
-Builds your image and pushes it to a local registry.
-If you don't have a registry spins it up, default registry is localhost:5050.
-It always build with one tag - "latest" and it is useful if you'd like to quickly rebuild some images
-
-Example command for Chainlink image (e2e/capabilities dir):
-ctf docker build -f ../../core/chainlink.Dockerfile -c ../.. -n chainlink
-
-You can reference this image in config as:
-localhost:5050/chainlink:latest`,
-
-						Action: func(c *cli.Context) error {
-							dockerfile := c.String("dockerfile")
-							buildContext := c.String("context")
-							imgName := c.String("image_name")
-							if dockerfile == "" || buildContext == "" || imgName == "" {
-								return errors.New(`dockerfile, build context and image name must be provided\nex.: -f ./core/chainlink.Dockerfile -c . -n chainlink`)
-							}
-							return BuildDocker(dockerfile, buildContext, imgName)
-						},
-					},
 				},
 			},
 			{

framework/components/clnode/clnode.go

@@ -147,7 +147,7 @@ func newNode(in *Input, pgOut *postgres.Output) (*NodeOut, error) {
 	if in.Node.Name != "" {
 		containerName = in.Node.Name
 	} else {
-		containerName = framework.DefaultTCName("clnode")
+		containerName = framework.DefaultTCName("node")
 	}
 
 	req := tc.ContainerRequest{