Thanks Matthew for sharing these details. What is the container address? Is that its host and ip address? Since annotations can be a JSON value, perhaps one annotation is enough with an object to encode the details you want nested in the annotation value. We might want a feature flag to attach this annotation (or only do it in certain deployments) since in a production setting this annotation will have little actionable value to end users.
-r On Thu, Dec 12, 2019 at 11:54 AM Matthew Hoffman <[email protected]> wrote: > Hello, > > I am working to integrate OpenWhisk with an open source container > debugging tool called CNTR. CNTR attaches containers given their > containerID (like those provided by docker ps and those used internally by > OpenWhisk). So, I would like to expose an activation’s corresponding > containerID. > > I have modified ContainerProxy.constructWhiskActivation to store the > containerID and containerAddress as additional annotations in the > activation result. This enables CNTR to attach the container of a > previously invoked lambda by making a REST API call given an activationId. > Can I get feedback on my approach? Would it be possible for me to submit > this as a merge request? > > — > Matthew Hoffman > Undergraduate at the University of Texas at Austin
