Adding in test-apps

Author: OskarLiew

python36-slim/test/test-app/.s2i/environment

@@ -0,0 +1 @@
+APP_FILE = service.py

python36-slim/test/test-app/.s2iignore

@@ -0,0 +1,8 @@
+# In this file you can add files/folders to ignore when deploying
+# Works similar to a .gitignore file
+
+# Ignore the .git folder to not only use committed code
+.git/
+
+# Test directory is not needed in production
+tests/

python36-slim/test/test-app/README.md

@@ -0,0 +1,37 @@
+# Daeploy project: my_project
+
+## Creating the service
+
+The ```service.py``` contains an example service and shows how to use the daeploy SDK.
+
+This example shows:
+
+- How to initiate a daeploy service
+- How to register changeable parameters
+- How to register functions as entrypoints
+- How to log from the service
+- How to send notifications from the service
+- How to start the service
+
+If the service requires external packages, they should be specified in the `requirements.txt` file.
+
+## Deploying the service
+
+The service can be deployed using the daeploy command-line interface:
+
+From a local directory or tarball (.tar.gz):
+
+```daeploy deploy myservice 0.0.1 <path_to_project>```
+
+From a git repository:
+
+```daeploy deploy myservice 0.0.1 --git <git_url>```
+
+## Documentation
+
+Full documentation of the SDK and the CLI can be found here: [https://vikinganalytics.github.io/daeploy-docs/](https://vikinganalytics.github.io/daeploy-docs/)
+
+## Extra
+
+If you want to change name of the service file ```service.py```, or deploy another file as the
+daeploy service then you have to change the ```APP_FILE``` key in the ```.s2i/environment``` file.

python36-slim/test/test-app/requirements.txt

@@ -0,0 +1 @@
+daeploy

python36-slim/test/test-app/service.py

@@ -0,0 +1,17 @@
+import logging
+from daeploy import service
+
+logger = logging.getLogger(__name__)
+
+service.add_parameter("greeting_phrase", "Hello")
+
+
+@service.entrypoint
+def hello(name: str) -> str:
+    greeting_phrase = service.get_parameter("greeting_phrase")
+    logger.info(f"Greeting someone with the name: {name}")
+    return f"{greeting_phrase} {name}"
+
+
+if __name__ == "__main__":
+    service.run()

python36-slim/test/test-app/tests/base_functionality_test.py

@@ -0,0 +1,27 @@
+from pathlib import Path
+
+# Change import if you have changed name of service.py
+import service as app
+
+# Read service source file
+SERVICE_DIR = Path(__file__).parent.parent
+service_path = (SERVICE_DIR / app.__name__).with_suffix(".py")
+with service_path.open("r") as file_handle:
+    service_code = file_handle.read()
+
+
+def test_service_run():
+    run_statement = "service.run()"
+    run_row = ""
+
+    for item in service_code.split("\n"):
+        if run_statement in item:
+            run_row = item
+
+    assert (
+        run_statement in run_row
+    ), f"For the service to run, the service code must end with {run_statement}"
+
+    run = run_row.find(run_statement)
+    comment = run_row.find("#")
+    assert comment == -1 or comment > run, f"{run_statement} commented out"

python36-slim/test/test-app/tests/user_test.py

@@ -0,0 +1,16 @@
+# Change import if you have changed name of service.py
+from daeploy.testing import patch
+import service
+
+# Test functions should always start with test_...
+# Daeploy tests use the pytest package
+
+# Example tests:
+
+
+def test_hello():
+    # Test that service.hello("Bob") returns what is expected
+    assert service.hello("Bob") == "Hello Bob"
+
+
+# Add your tests here

python37-slim/test/test-app/.s2i/environment

@@ -0,0 +1 @@
+APP_FILE = service.py

python37-slim/test/test-app/.s2iignore

@@ -0,0 +1,8 @@
+# In this file you can add files/folders to ignore when deploying
+# Works similar to a .gitignore file
+
+# Ignore the .git folder to not only use committed code
+.git/
+
+# Test directory is not needed in production
+tests/

python37-slim/test/test-app/README.md

@@ -0,0 +1,37 @@
+# Daeploy project: my_project
+
+## Creating the service
+
+The ```service.py``` contains an example service and shows how to use the daeploy SDK.
+
+This example shows:
+
+- How to initiate a daeploy service
+- How to register changeable parameters
+- How to register functions as entrypoints
+- How to log from the service
+- How to send notifications from the service
+- How to start the service
+
+If the service requires external packages, they should be specified in the `requirements.txt` file.
+
+## Deploying the service
+
+The service can be deployed using the daeploy command-line interface:
+
+From a local directory or tarball (.tar.gz):
+
+```daeploy deploy myservice 0.0.1 <path_to_project>```
+
+From a git repository:
+
+```daeploy deploy myservice 0.0.1 --git <git_url>```
+
+## Documentation
+
+Full documentation of the SDK and the CLI can be found here: [https://vikinganalytics.github.io/daeploy-docs/](https://vikinganalytics.github.io/daeploy-docs/)
+
+## Extra
+
+If you want to change name of the service file ```service.py```, or deploy another file as the
+daeploy service then you have to change the ```APP_FILE``` key in the ```.s2i/environment``` file.