CMCDragonkai

Vault schemas can be nested. ``` { "dir1": { ... } "dir2": { ... } } ``` We have to differentiate directories from files. Which could be done with the...

Vault schemas are just directory schemas. On 30 September 2021 9:45:06 am AEST, Josh ***@***.***> wrote: >So this means a directory would also have its own vault schema applied to...

These would be 2 different schemas so they are independent. On 30 September 2021 10:15:00 am AEST, Josh ***@***.***> wrote: >So I found some more discussion hidden away in a...

As per discussion in https://github.com/MatrixAI/Polykey-CLI/issues/296#issuecomment-2452546309, it turns out we can implement an idea I call egress schemas. That is separate from vault and secret schemas. As vault and secret schemas...

Another thing to realise here is that the usage of references like `op://a/b/c` like in https://blog.1password.com/delete-your-example-env-file/ is a common idea, however I believe this is a control-plane concern, and shouldn't...

Related to https://github.com/MatrixAI/Polykey/issues/386?

A couple ways to do this: 1. In terms of fixing this, just mock the handler - wrap the old implementation, and then run an additional function at the end,...

Closing in favour of #835

This https://github.com/MatrixAI/Polykey-CLI/issues/40#issuecomment-1907579883 might be relevant here too.

For AWS Secrets Manager, an example of non-plugin push integration would be scripting `pk` with the `aws` CLI. https://docs.aws.amazon.com/cli/latest/reference/secretsmanager/index.html#cli-aws-secretsmanager Also see the difference between parameter store and secrets manager here:...