Sign inSign up

indigopaas/federation-manager

By indigopaas

•Updated about 1 year ago

Image
0

904

indigopaas/federation-manager repository overview

⁠Developers

⁠Testing OPA within container

The containerized instance of OPA needs the policies (opa/policy.rego) and the data (opa/data.json) used to evaluate the input.

The following docker-compose file:

  • copies in the /fedmgr folder the ./opa folder contained in this repository.
  • starts opa in server mode
  • loads the fedmgr package and serves it on localhost:8181/v1/data/fedmgr.
# compose.yaml
services:
  opa:
    image: openpolicyagent/opa
    ports:
      - 8181:8181
    volumes:
      - ./opa:/fedmgr:ro
    command: run --server --log-level debug /fedmgr
docker compose up -d

Once OPA is up and running we can interrogate its endpoints to evaluate the inpute contained in v1-data-input.json. Here we give an example of the input to provide to the OPA REST API.

# v1-data-input.json
{
    "input": {
        "authorization": "Bearer <token>"
    }
}
curl localhost:8181/v1/data/fedmgr/user_roles -d @v1-data-input.json -H 'Content-Type: application/json'
⁠Testing SocketIO with python client

In the examples folder we provide a python script with a Socket.IO client. It tries to connect to the /site_admin namespace and emit a message.

Since endpoints requires a valid token, this example expects the access token as an input to the --token (or -t) argument. Alternatively you can set the $SOCKETIO_CLIENT_TOKEN env var.

python examples/client.py -t <TOKEN>

For the example client to work you need a running instance of the application.

You can copy and edit that file to make more complexes examples or tests.

Tag summary

Content type

Image

Digest

sha256:3d386cd0d…

Size

116.4 MB

Last updated

about 1 year ago

docker pull indigopaas/federation-manager:jenkins-python3.10