Toby Archer

Thanks for the input. As you mentioned, I think s3fs is a very good starting point. I will make a note to play around with setting up Polaris + s3fs...

Would there be any other non-filesystem, S3-like backends that could potentially be supported by Polaris? I know Google Drive is often used an archive tool, but I'm not sure about...

🙏 Number 1 use case in my mind for this is to provide a `ansible_docker_host` variable with the container name, to be used with the [Ansible docker connection plugin](https://docs.ansible.com/ansible/latest/collections/community/docker/docker_connection.html#ansible-collections-community-docker-docker-connection) Actually...

Visiting that now, that's true, however for the hostname to work we actually need to _remove_ the `ansible_host` var, as here https://github.com/srl-labs/containerlab/pulls?q=is%3Apr+ansible+#issuecomment-1047270956 Would we want something to extend this config...

The project seems semi-abandoned. I suggest forgoing the install script and installing with homebrew. ``` $ brew upgrade kryptco/tap/kr && brew install kr ```

Thanks for the clarification. I wonder if it's of value to add the ability to create a service under the ThanosSpec, targeting the related instances sidecar? This might be super...

I feel a new rule that's responsible for the dependency tracking and resolution of bases, resources, and patches, with `kustomization.yaml` being the entry point would provie useful, with the perceived...

> would advice to design and prototype a new rule rules_kustomize Is there an outlined process for going through the design and prototyping of such a rule?

I personally am a fan of exposing a `goose.Registered` API, that gives you some control over `registeredGoMigrations` For example, the simplest compiled migration binary would look like: ```go package main...

Would love to see more input and build some sort of directions for this