challenge-assignment-plugin-server-python

flowchart LR
   subgraph AccelByte Gaming Services
   CL[gRPC Client]
   end
   subgraph Extend Override App
   SV["gRPC Server"]
   end
   CL --- SV

AccelByte Gaming Services (AGS) features can be customized using Extend Override apps. An Extend Override app is basically a gRPC server which contains one or more custom functions which can be called by AGS instead of the default functions.

Overview

This repository serves as a template project for an Extend Override app for challenge assignment function written in C#. You can clone this repository and start implementing custom functions which can then be called by AGS.

By using this repository as a template project, you will get the recommended authentication and authorization implemented out-of-the-box. You will also get some instrumentation for observability so that metrics, traces, and logs will be available when the app is deployed.

As an example to get you started, this template project contains sample custom functions for connecting this app onto challenge service to be used for challenge assignment.

Prerequisites

Windows 11 WSL2 or Linux Ubuntu 22.04 with the following tools installed.

a. Bash
```
bash --version

GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
...
```
b. Make
- To install from Ubuntu repository, run: sudo apt update && sudo apt install make
```
make --version

GNU Make 4.3
...
```
c. Docker (Docker Engine v23.0+)
- To install from Ubuntu repository, run: sudo apt update && sudo apt install docker.io
- Add your user to docker group: sudo usermod -aG docker $USER
- Log out and log back in so that the changes take effect
```
docker version

...
Server: Docker Desktop
 Engine:
  Version:          24.0.5
...
```
d. Python 3.10
- On Linux Ubuntu:
  
  To install from the Ubuntu repository, run sudo apt update && sudo apt install python3 python3-venv.
- On Windows or macOS:
  
  Use the available installer here.
```
python3 --version

Python 3.10.12
```
e. Postman
- Use binary available here
f. extend-helper-cli
- Use the available binary from extend-helper-cli.
g. Local tunnel service that has TCP forwarding capability, such as:
- Ngrok
  
  Need registration for free tier. Please refer to ngrok documentation for a quick start.
- Pinggy
  
  Free to try without registration. Please refer to pinggy documentation for a quick start.
Access to AGS environment.

a. Base URL
- For Starter tier e.g. https://spaceshooter.prod.gamingservices.accelbyte.io
- For Premium tier e.g. https://dev.accelbyte.io
b. Create a Game Namespace if you don't have one yet. Keep the Namespace ID.

c. Create an OAuth Client with confidential client type. Keep the Client ID and Client Secret.

Setup

To be able to run this app, you will need to follow these setup steps.

Create a docker compose .env file by copying the content of .env.template file.

⚠️ The host OS environment variables have higher precedence compared to .env file variables: If the variables in .env file do not seem to take effect properly, check if there are host OS environment variables with the same name. See documentation about docker compose environment variables precedence for more details.

Fill in the required environment variables in .env file as shown below.

AB_BASE_URL=https://demo.accelbyte.io     # Base URL of AccelByte Gaming Services environment
AB_CLIENT_ID='xxxxxxxxxx'                 # Client ID from the Prerequisites section
AB_CLIENT_SECRET='xxxxxxxxxx'             # Client Secret from the Prerequisites section
AB_NAMESPACE='xxxxxxxxxx'                 # Namespace ID from the Prerequisites section
PLUGIN_GRPC_SERVER_AUTH_ENABLED=true      # Enable or disable access token validation

:info: In this sample app, PLUGIN_GRPC_SERVER_AUTH_ENABLED is true by default: If it is set to false, th gRPC server can be invoked without an AGS access token. This option is provided for development purpose only. It is recommended to enable gRPC server access token validation in production environment.

For more options, create src/AccelByte.PluginArch.ChallengeAssignment.Demo.Server/appsettings.Development.json and fill in the required configuration.

{
   "EnableAuthorization": true,                    // Enable or disable access token and permission check (env var: PLUGIN_GRPC_SERVER_AUTH_ENABLED)
   "RevocationListRefreshPeriod": 60,
   "AccelByte": {
      "BaseUrl": "https://demo.accelbyte.io",      // Base URL (env var: AB_BASE_URL)
      "ClientId": "xxxxxxxxxx",                    // Client ID (env var: AB_CLIENT_ID)    
      "ClientSecret": "xxxxxxxxxx",                // Client Secret (env var: AB_CLIENT_SECRET)
      "AppName": "CHALLENGEASGGRPCSERVICE",
      "TraceIdVersion": "1",
      "Namespace": "xxxxxxxxxx",                   // Namespace ID (env var: AB_NAMESPACE)
      "EnableTraceId": true,
      "EnableUserAgentInfo": true,
      "ResourceName": "CHALLENGEASGGRPCSERVICE"
   }
}

⚠️ Environment variable values will override related configuration values in this file.

Building

To build this app, use the following command.

make build

Running

To (build and) run this app in a container, use the following command.

docker compose up --build

Testing

Test in Local Development Environment

⚠️ To perform the following, make sure PLUGIN_GRPC_SERVER_AUTH_ENABLED is set to false: Otherwise, the gRPC request will be rejected by the gRPC server.

The custom functions in this app can be tested locally using postman.

Run this app by using the command below.
```
docker compose up --build
```
Open postman, create a new gRPC request, and enter localhost:6565 as server URL.

⚠️ If you are running grpc-plugin-dependencies stack alongside this app as mentioned in Test Observability: Enter localhost:10000 instead of localhost:6565. This way, the gRPC server will be called via Envoy service within grpc-plugin-dependencies stack instead of directly.

Continue by selecting AssignmentFunction/Assign method and invoke it with the sample message below.

{
   "goals": [
      {
            "code": "goal-code",
            "challengeCode": "challenge-code",
            "name": "goal name",
            "isActive": true,
            "tags": [
               {
                  "name": "big goal"
               }
            ],
            "requirements": [
               {
                  "operator": "AND",
                  "predicates": [
                        {
                           "parameterName": "mmr",
                           "parameterType": "STATISTIC",
                           "matcher": "GREATER_THAN",
                           "targetValue": 100
                        }
                  ]
               }
            ],
            "rewards": [
               {
                  "type": "STATISTIC",
                  "itemId": "mmr",
                  "itemName": "more mmr",
                  "quantity": 10
               }
            ],
            "createdAt": {
               "seconds": "5095510",
               "nanos": 728418711
            },
            "updatedAt": {
               "seconds": "7873407235",
               "nanos": -217262300
            }
      }
   ],
   "namespace": "namespace",
   "userId": "dcd3fc9c238a4c6d9cd8c5da2f595bd6"
}

The response will be the list of goals chosen to be assigned to user

{
   "assignedGoals":  [
      {
            "code": "goal-code",
            "challengeCode": "challenge-code",
            "name": "goal name",
            "isActive": true,
            "tags": [
               {
                  "name": "big goal"
               }
            ],
            "requirements": [
               {
                  "operator": "AND",
                  "predicates": [
                        {
                           "parameterName": "mmr",
                           "parameterType": "STATISTIC",
                           "matcher": "GREATER_THAN",
                           "targetValue": 100
                        }
                  ]
               }
            ],
            "rewards": [
               {
                  "type": "STATISTIC",
                  "itemId": "mmr",
                  "itemName": "more mmr",
                  "quantity": 10
               }
            ],
            "createdAt": {
               "seconds": "5095510",
               "nanos": 728418711
            },
            "updatedAt": {
               "seconds": "7873407235",
               "nanos": -217262300
            }
      }
   ],
   "namespace": "namespace",
   "userId": "dcd3fc9c238a4c6d9cd8c5da2f595bd6"
}

Test with AccelByte Gaming Services

To test the app, which runs locally with AGS, the gRPC server needs to be connected to the internet. To do this without requiring public IP, you can use local tunnel service.

Run this app by using command below.
```
docker compose up --build
```
Expose gRPC server TCP port 6565 in local development environment to the internet. Simplest way to do this is by using local tunnel service provider.
- Sign in to ngrok and get your authtoken from the ngrok dashboard and set it up in your local environment. And, to expose gRPC server use following command:
```
ngrok tcp 6565
```
- Or alternatively, you can use pinggy and use only ssh command line to setup simple tunnel. Then to expose gRPC server use following command:
```
ssh -p 443 -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -R0:127.0.0.1:6565 [email protected]
```
Please take note of the tunnel forwarding URL, e.g., http://0.tcp.ap.ngrok.io:xxxxx or tcp://xxxxx-xxx-xxx-xxx-xxx.a.free.pinggy.link:xxxxx.

❗ You may also use other local tunnel service and different method to expose the gRPC server port (TCP) to the internet.

⚠️ If you are running grpc-plugin-dependencies stack alongside this app as mentioned in Test Observability: Run the above command in grpc-plugin-dependencies directory instead of this app directory and change tunnel local port from 6565 to 10000. This way, the gRPC server will be called via Envoy service within grpc-plugin-dependencies stack instead of directly.
Create an OAuth Client with confidential client type with the following permissions. Keep the Client ID and Client Secret.
- For AGS Private Cloud customers:
  - ADMIN:NAMESPACE:{namespace}:CHALLENGE:PLUGIN [CREATE,READ,UPDATE,DELETE]
  - NAMESPACE:{namespace}:CHALLENGE:PROGRESSION [READ]
  - ADMIN:NAMESPACE:{namespace}:INFORMATION:USER:* [DELETE]
- For AGS Shared Cloud customers:
  - Challenge -> Custom Configuration (Read, Create, Update, Delete)
  - Challenge -> Challenge Progression (Read, Create, Update, Delete)
  - IAM -> Users (Delete)
⚠️ Oauth Client created in this step is different from the one from Prerequisites section: It is required by the Postman collection in the next step to register the gRPC Server URL and also to create and delete test users.
Import the Postman collection in order to simulate the extend app flow. Pay attention to this app console log when extend app flow is running. At least one of the gRPC Server methods should get called when you run all the requests in the collection.

Test Observability

To be able to see the how the observability works in this app locally, there are few things that need be setup before performing tests.

Uncomment loki logging driver in docker-compose.yaml
```
 # logging:
 #   driver: loki
 #   options:
 #     loki-url: http://host.docker.internal:3100/loki/api/v1/push
 #     mode: non-blocking
 #     max-buffer-size: 4m
 #     loki-retries: "3"
```
⚠️ Make sure to install docker loki plugin beforehand: Otherwise, this app will not be able to run. This is required so that container logs can flow to the loki service within grpc-plugin-dependencies stack. Use this command to install docker loki plugin: docker plugin install grafana/loki-docker-driver:latest --alias loki --grant-all-permissions.
Clone and run grpc-plugin-dependencies stack alongside this app. After this, Grafana will be accessible at http://localhost:3000.
```
git clone https://github.com/AccelByte/grpc-plugin-dependencies.git
cd grpc-plugin-dependencies
docker-compose up
```
❗ More information about grpc-plugin-dependencies is available here.
Perform testing. For example, by following Test in Local Development Environment or Test with AccelByte Gaming Services.

Deploying

After completing testing, the next step is to deploy your app to AccelByte Gaming Services.

Create an Extend Override app

If you do not already have one, create a new Extend Override App.

On the App Detail page, take note of the following values.
- Namespace
- App Name
Build and Push the Container Image

Use extend-helper-cli to build and upload the container image.
```
extend-helper-cli image-upload --login --namespace <namespace> --app <app-name> --image-tag v0.0.1
```
⚠️ Run this command from your project directory. If you are in a different directory, add the --work-dir <project-dir> option to specify the correct path.
Deploy the Image

On the App Detail page:
- Click Image Version History
- Select the image you just pushed
- Click Deploy Image

Next Step

Proceed by modifying this Extend Override app template to implement your own custom logic. For more details, see here.

Name		Name	Last commit message	Last commit date
Latest commit History 41 Commits
demo		demo
proto		proto
src		src
.dockerignore		.dockerignore
.env.template		.env.template
.gitignore		.gitignore
Dockerfile		Dockerfile
Makefile		Makefile
README.md		README.md
docker-compose.yaml		docker-compose.yaml
proto.sh		proto.sh
requirements-dev.txt		requirements-dev.txt
requirements.txt		requirements.txt

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Repository files navigation

challenge-assignment-plugin-server-python

Overview

Prerequisites

Setup

Building

Running

Testing

Test in Local Development Environment

Test with AccelByte Gaming Services

Test Observability

Deploying

Next Step

About

Uh oh!

Releases

Packages

Uh oh!

Contributors 4

Uh oh!

Languages

AccelByte/challenge-assignment-plugin-server-python

Folders and files

Latest commit

History

Repository files navigation

challenge-assignment-plugin-server-python

Overview

Prerequisites

Setup

Building

Running

Testing

Test in Local Development Environment

Test with AccelByte Gaming Services

Test Observability

Deploying

Next Step

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors 4

Uh oh!

Languages

Packages