Austin Godber

I think this issue will need to be implemented in each individual asset's API package but there should probably be a shared base class in terafoundation that has common properties...

In addition to S3 connector specific addition of `caCertificate`, lets ad a top level property in `terafoundation` called `globalCaCertificate`, which is also a multiline string meant to contain a certificate...

For now we going to de-scope the `globalCaCertificate`. It's not strictly needed and implementing it is introducing it is getting messy.

This has been completed for the `s3Connector` case, other cases remain unimplemented.

I think fully namespacing things like `Elasticsearch.ClientResponse.IndicesGetMappingResponse` makes sense and is pretty much a must. And isn't there `import Foo as` type syntax that can reduce the need for the...

Note, these failures are not due to a missing image, but because running yarn fails https://github.com/terascope/teraslice/actions/runs/8975998521/job/24655637262

@sotojn added some docs here: https://github.com/terascope/teraslice/blob/master/docs/development/node.md But they don't show up in the site under the development page: https://terascope.github.io/teraslice/docs/development/overview There's probably an index somewhere or some frontmatter we need to...

Oh, it shows up as it's own page here: https://terascope.github.io/teraslice/docs/development/node Maybe the use of `sidebar_label: Node` somehow breaks it out of the Development tab its supposed to be under.

The `Port is already in-use` issue could be a previous shutdown container port being in `TIME_WAIT` (2 min timeout).

This looks new https://github.com/terascope/teraslice/actions/runs/10728060227/job/29751854383#step:9:250 ``` ℹ info Teraslice node version: undefined ✖ error Expected node version(20) does not match teraslice node version(undefined) error Command failed with exit code 1. ```