add template

.gitignore

+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
\ No newline at end of file

.gitlab-ci.yml

+stages:
+  - build
+
+test:
+  image: python:3.9
+  stage: build
+  services:
+      - name: gitlab.memri.io:5050/memri/pod:dev-latest
+        alias: pod
+        entrypoint:
+          - "/pod"
+          - "--owners=ANY"
+          - "--insecure-non-tls=0.0.0.0"
+  before_script:
+      - pip install -e .
+  script:
+  - curl http://pod:3030/version
+  - export POD_ADDRESS='http://pod:3030'
+  - pytest
+
+build_image:
+  only:
+    - dev
+    - main
+  stage: build
+  before_script:
+    - echo "Building docker image..."
+  image: 
+        # We recommend using the CERN version of the Kaniko image: gitlab-registry.cern.ch/ci-tools/docker-image-builder
+        name: gcr.io/kaniko-project/executor:debug
+        entrypoint: [""]
+  script:
+        # Prepare Kaniko configuration file
+        - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
+        # Build and push the image from the Dockerfile at the root of the project.
+        # To push to a specific docker tag, amend the --destination parameter, e.g. --destination $CI_REGISTRY_IMAGE:$CI_BUILD_REF_NAME
+        # See https://docs.gitlab.com/ee/ci/variables/predefined_variables.html#variables-reference for available variables
+        - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --build-arg CI_JOB_TOKEN=$CI_JOB_TOKEN --destination $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG-$CI_COMMIT_SHORT_SHA --destination $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG-latest

.pre-commit-config.yaml

+repos:
+  - repo: https://github.com/charliermarsh/ruff-pre-commit
+    # Ruff version.
+    rev: 'v0.0.257'
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+  - repo: https://github.com/psf/black
+    rev: '23.1.0'
+    hooks:
+    -   id: black
+        args: [--line-length=120]
\ No newline at end of file

Dockerfile

+FROM python:3.9-slim-buster
+ENV DEBIAN_FRONTEND=noninteractive
+
+WORKDIR /usr/cookiecutter-test-plugin/
+
+# In order to leverage docker caching, copy only the minimal
+# information needed to install dependencies
+COPY ./pyproject.toml ./pyproject.toml
+COPY ./setup.py ./setup.py
+COPY ./README.md ./README.md
+COPY ./cookiecutter_test_plugin ./cookiecutter_test_plugin
+
+RUN pip3 install -e .
+
+CMD ["run_plugin", "--read_args_from_env", "True"]

README.md

-# Cookiecutter Test Plugin
+# cookiecutter-test-plugin
 
+This is a cookiecutter test plugin.
 
+# Install
 
-## Getting started
+To install as a Python package, run:
+```bash
+pip install -e .
+```
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+# Run
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+Make sure you have a pod running. Then, you can run the plugin locally with the run_plugin CLI:
 
-## Add your files
+```bash
+run_plugin --metadata "metadata.json"
+```
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+# Docker
 
 ```
-cd existing_repo
-git remote add origin https://gitlab.memri.io/eelcovdw/cookiecutter-test-plugin.git
-git branch -M main
-git push -uf origin main
+docker build -t $package_name .
 ```
 
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.memri.io/eelcovdw/cookiecutter-test-plugin/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
+To run the plugin:
 
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+```
+simulate_run_plugin_from_frontend --metadata "metadata.json"
+```
\ No newline at end of file

cookiecutter_test_plugin/plugin.py

+from loguru import logger
+from pymemri.plugin.pluginbase import PluginBase
+
+
+class CookiecutterTestPlugin(PluginBase):
+    schema_classes = []
+
+    def __init__(self, **kwargs):
+        logger.info(f"Starting {self.__class__.__name__}...")
+        super().__init__(**kwargs)
+
+    def run(self):
+        raise NotImplementedError()

metadata.json

+{
+    "pluginType": "app",
+    "name": "cookiecutter-test-plugin",
+    "container": "gitlab.memri.io:5050/eelcovdw/cookiecutter-test-plugin:main-latest",
+    "icon": null,
+    "pluginModule": "cookiecutter_test_plugin.plugin",
+    "pluginName": "CookiecutterTestPlugin",
+    "description": "This is a cookiecutter test plugin."
+}
\ No newline at end of file

pyproject.toml

+[project]
+name = "cookiecutter-test-plugin"
+version = "0.0.1"
+authors = [
+    {name = "Eelco van der Wel", email = "eelco@memri.io"},
+]
+description = "This is a cookiecutter test plugin."
+classifiers = [
+    "Programming Language :: Python :: 3",
+]
+requires-python = ">=3.7"
+dependencies = [
+    "pymemri",
+    "loguru",
+]
+
+[project.optional-dependencies]
+dev = [
+    "pre-commit",
+    "pytest",
+]
+
+[build-system]
+requires = ["setuptools>=64.0.0",]
+build-backend = "setuptools.build_meta"
+
+[project.readme]
+file = "README.md"
+content-type = "text/markdown"
+
+[project.license]
+file = "LICENSE"
+
+[project.urls]
+homepage = "https://gitlab.memri.io/eelcovdw/cookiecutter-test-plugin"
+
+[tool.setuptools]
+license-files = ["LICENSE"]
+include-package-data = false
+
+[tool.setuptools.packages.find]
+exclude = ["nbs*", "tests*"]
+
+[tool.ruff]
+select = ["E", "F", "C90", "I", "N", "S", "B", "PL"]
+ignore = [
+    "S101", # Allow assert 
+    "B905", # Allow zip without `strict=` parameter
+]
+line-length = 120
+
+[tool.black]
+line-length = 120

setup.py

+import setuptools
+
+if __name__ == "__main__":
+    setuptools.setup()

tests/test_plugin.py

+import json
+from typing import Any, Dict
+
+import pytest
+from pymemri.plugin.pluginbase import PluginBase, get_plugin_cls
+from pymemri.pod.client import PodClient
+
+
+@pytest.fixture
+def client():
+    return PodClient()
+
+
+@pytest.fixture
+def metadata() -> Dict[str, Any]:
+    with open("./metadata.json") as f:
+        metadata = json.load(f)
+    return metadata
+
+
+def test_init_plugin_from_metadata(metadata: Dict[str, Any], client: PodClient):
+    # Import plugin
+    plugin_cls = get_plugin_cls(metadata["pluginModule"], metadata["pluginName"])
+    assert issubclass(plugin_cls, PluginBase)
+
+    # Init plugin
+    _ = plugin_cls(client=client)