Intercepts

Description and operation

General

An intercept sends all traffic of one environment service to a workspace of your session. The code that you edit in the workspace answers real requests from the rest of the environment, with no build and no deploy. Callers do not change: they use the same name and port as before.

An intercept is for the whole environment, not only for your session. Every caller of the service reaches your workspace, including the workspaces of other sessions on the environment. This is what lets several developers test their changes against each other. See Ways to work.

Ports

By default each port of the service goes to the same port in the workspace. Give ports to map a service port to another workspace port, for example api:8080 to port 3000, where a development server listens. Callers still use port 8080.

Switch

Traffic moves only when the workspace can take it, so callers never reach a workspace that is not ready.

If the switch cannot be made, proxy is failed and the service keeps its traffic. An intercept is in force when the service in the environment's service_status shows interceptedBy.

Lifecycle

• Stays until removed. An intercept stays in the session's intercepts until you remove it.
• Workspace stopped or not answering. If the workspace stops or does not answer for 30 seconds, traffic goes back to the service. The intercept is kept, and takes hold again when the workspace is back.
• Released with the session. Deleting the workspace, changing the session's environment, ending the session or deleting the environment releases the intercept.
• Owned by one session. Only the session that holds an intercept can remove it. Another session that asks for the same service is refused, with the name of the holder.

Limits

Tasks

Intercept a service

Reason for the task: Run a service from your workspace against the rest of the environment.

Job set-up

• Access: you.
• References: POST /v1/sessions/{id}/intercepts.

Procedure

1. Create the intercept. Map ports with ports when the workspace listens on another port; this example sends 8080 to 3000.

   PythonCopy

   from kloudlite import Kloudlitekl = Kloudlite()kl.sessions.intercept(session="dev", service="api", workspace="backend", ports={8080: 3000})

   TypeScriptCopy

   import { Kloudlite } from "./index.ts";const kl = new Kloudlite();await kl.sessions.intercept({ session: "dev", service: "api", workspace: "backend", ports: { 8080: 3000 } });

   GoCopy

   kl := kloudlite.New(kloudlite.Options{})_, err := kl.Sessions.Intercept(kloudlite.InterceptService{Session: "dev", Service: "api", Workspace: "backend", Ports: map[int]int{8080: 3000}})if err != nil {    log.Fatal(err)}

   RubyCopy

   require_relative "kloudlite"kl = Kloudlite::Client.newkl.sessions.intercept(session: "dev", service: "api", workspace: "backend", ports: { 8080 => 3000 })

   JavaCopy

   var kl = new Kloudlite();kl.sessions().intercept(new Kloudlite.InterceptService()    .session("dev").service("api").workspace("backend").ports(Map.of(8080, 3000)));

   CLICopy

   kloudlite sessions intercept api --workspace backend --port 8080=3000 --session dev

Close-out

1. Wait until the service in service_status shows interceptedBy and proxy is ready.

Show the intercepts

Reason for the task: Check which services your session routes to a workspace.

Job set-up

• Access: you.
• References: GET /v1/sessions/{id}.

Procedure

1. Show the session's intercepts.

   PythonCopy

   for i in kl.sessions.get(session="dev")["intercepts"]:    print(i["service"], i["workspace"], i["ports"])

   TypeScriptCopy

   const s: any = await kl.sessions.get({ session: "dev" });for (const i of s.intercepts) console.log(i.service, i.workspace, i.ports);

   GoCopy

   s, err := kl.Sessions.Get("dev")if err != nil {    log.Fatal(err)}for _, v := range s["intercepts"].([]any) {    i := v.(map[string]any)    fmt.Println(i["service"], i["workspace"], i["ports"])}

   RubyCopy

   kl.sessions.get(session: "dev")["intercepts"].each { |i| puts "#{i['service']} #{i['workspace']} #{i['ports']}" }

   JavaCopy

   System.out.println(kl.sessions().get("dev"));

   CLICopy

   kloudlite sessions get dev

Close-out

1. Make sure that every service that you intercepted is listed.

Remove an intercept

Reason for the task: Give a service its traffic back.

Job set-up

• Access: you.
• References: DELETE /v1/sessions/{id}/intercepts/{service}.

Procedure

1. Remove the intercept.

   PythonCopy

   kl.sessions.release(session="dev", service="api")

   TypeScriptCopy

   await kl.sessions.release({ session: "dev", service: "api" });

   GoCopy

   if err := kl.Sessions.Release(kloudlite.ReleaseService{Session: "dev", Service: "api"}); err != nil {    log.Fatal(err)}

   RubyCopy

   kl.sessions.release(session: "dev", service: "api")

   JavaCopy

   kl.sessions().release(new Kloudlite.ReleaseService().session("dev").service("api"));

   CLICopy

   kloudlite sessions release api --session dev

Close-out

1. Show the intercepts as in task 002. Make sure that the service is gone.

Troubleshooting