A lazy Sunday afternoon and my interest was piqued by XML-RPC Client A very basic XML-RPC client wrapped in a Cloud Functions function: main.py: import functions_framework import os import xmlrpc.client endpoint = os.get_env("ENDPOINT") proxy = xmlrpc.client.ServerProxy(endpoint) @functions_framework.http def add(request): print(request) rqst = request.get_json(silent=True) resp = proxy.add( {"x":{ "real":rqst["x"]["real"], "imag":rqst["x"]["imag"] }, "y":{ "real":rqst["y"]["real"], "imag":rqst["y"]["imag"] } }) return resp requirements.txt: functions-framework==3.* Run it: python3 -m venv venv source venv/bin/activate python3 -m pip install --requirement requirements.

I naively (!) began exploring JSON marshaling of Protobufs in rust. Other protobuf language SDKs include JSON marshaling making the process straightforward. I was to learn that, in rust, it’s not so simple. Unfortunately, for me, this continues to discourage my further use of rust (rust is just hard). My goal was to marshal an arbitrary protocol buffer message that included a oneof feature. I was unable to JSON marshal the rust generated by tonic for such a message.

Responded to Get Custom K8s Resource using Python and found the CustomObjectsApi documentation unclear. If you have a cluster and a kubeconfig file with a correctly configured current-context, so that you can successfully: PLURAL="checks" kubectl get ${PLURAL} \ --all-namespaces NOTE I’m using Ackal’s CRDs in these examples. Then you can use the following code to access the cluster’s REST API server to enumerate its CRDs: main.py: from __future__ import print_function from kubernetes import client, config from kubernetes.

Python’s Protocol Buffers code-generation using protoc has had significant changes that can cause developers… “challenges”. This post summarizes my experience of these mostly to save me from repreatedly recreating this history for myself when I forget it. Version change Generated code change Implementation Backends I’ll use this summarized table of proto and the Pypi library’s history in this post. protoc refers to the compiler that supports code-generation in multiple languages. protobuf refers to the corresponding Python (runtime) library on Pypi:

Phew! Programmitcally deploying Cloud Run services should be easy but it didn’t find it so. My issues were that the Cloud Run Admin (!) API is poorly documented and it uses non-standard endpoints (thanks Sal!). Here, for others who may struggle with this, is how I got this to work. Goal Programmatically (have Golang, Python, want Rust) deploy services to Cloud Run. i.e. achieve this: gcloud run deploy ${NAME} \ --image=${IMAGE} \ --platform=managed \ --no-allow-unauthenticated \ --region=${REGION} \ --project=${PROJECT} TRICK --log-http is your friend

A friend mentioned OriginStamp to me. NB There are 2 sites: originstamp.com and originstamp.org. It’s an interesting project. It’s a solution for providing auditable proof that you had a(ccess to) some digital thing before a certain date. OriginStamp provides user-|developer-friendly means to submit files|hashes (of your content) and have these bundled into transactions that are submitted to e.g. bitcoin. I won’t attempt to duplicate the narrative here, review OriginStamp’s site and some of its content.

I’ve been noodling around with another Trillian personality. Another in a theme that interests me in providing tamperproof logs for the packages in the popular package management registries. The Golang team recently announced Go Module Mirror which is built atop Trillian. It seems to me that all the package registries (Go Modules, npm, Maven, NuGet etc.) would benefit from tamperproof logs hosted by a trusted 3rd-party. As you may have guessed, PyPi Transparency is a log for PyPi packages.