Initial commit

Author: iciclespider

.gitignore

@@ -0,0 +1,210 @@
+# Emacs
+*~
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$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
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.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/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

CloudOps.groovy

@@ -0,0 +1,25 @@
+cloudops.dockerImage {
+
+    container {
+        name 'podman'
+        image 'quay.io/podman/stable:latest'
+        requests {
+            cpu '1'
+            memory '4Gi'
+        }
+        root true
+        privileged true
+    }
+
+    build { context ->
+        def arches = ['amd64', 'arm64']
+        arches.each { arch ->
+            container('podman') {
+                sh "podman build --platform=linux/$arch --tag=$arch ."
+                sh "podman image save --format docker-archive localhost/$arch --output image.$arch"
+            }
+            sh "crossplane xpkg build --package-root=package --embed-runtime-image-tarball=image.$arch --package-file=xpkg.$arch"
+        }
+        sh "crossplane xpkg push --package-files=${arches.collect{"xpkg.$it"}.join(',')} $context.INTERIM_IMAGE"
+    }
+}

Dockerfile

@@ -0,0 +1,43 @@
+# syntax=docker/dockerfile:1
+
+# It's important that this is Debian 12 to match the distroless image.
+FROM debian:12-slim AS build
+
+#RUN --mount=type=cache,target=/var/lib/apt/lists \
+#    --mount=type=cache,target=/var/cache/apt \
+RUN \
+    rm -f /etc/apt/apt.conf.d/docker-clean \
+    && apt-get update \
+    && apt-get install --no-install-recommends --yes python3-venv git
+
+# Don't write .pyc bytecode files. These speed up imports when the program is
+# loaded. There's no point doing that in a container where they'll never be
+# persisted across restarts.
+ENV PYTHONDONTWRITEBYTECODE=true
+
+# Use Hatch to build a wheel. The build stage must do this in a venv because
+# Debian doesn't have a hatch package, and it won't let you install one globally
+# using pip.
+WORKDIR /build
+#RUN --mount=target=. \
+#    --mount=type=cache,target=/root/.cache/pip \
+COPY . /build
+RUN \
+    python3 -m venv /venv/build \
+    && /venv/build/bin/pip install hatch \
+    && /venv/build/bin/hatch build -t wheel /whl
+
+# Create a fresh venv and install only the function wheel into it.
+#RUN --mount=type=cache,target=/root/.cache/pip \
+RUN \
+    python3 -m venv /venv/fn \
+    && /venv/fn/bin/pip install /whl/*.whl
+
+# Copy the function venv to our runtime stage. It's important that the path be
+# the same as in the build stage, to avoid shebang paths and symlinks breaking. 
+FROM gcr.io/distroless/python3-debian12 AS image
+WORKDIR /
+USER nonroot:nonroot
+COPY --from=build --chown=nonroot:nonroot /venv/fn /venv/fn
+EXPOSE 9443
+ENTRYPOINT ["/venv/fn/bin/function"]