I'm also using Ory Network and trying to think through configuration management across environments. We're taking a config-as-code approach with json config files that will go through tokenization process during deploy to each environment. However, I want to do a review of existing config to evaluate what we will need to customize. Is there a good resource (in docs or in the Github repo or something?) that lays out what all can be configured for Ory Network using json files and CLI commands?

I guess the Ory CLI doc is the right place to start. As said in the doc, most of the Ory services (Kratos, Hydra, Keto…) configuration keys can be used. Except does that would configure the Ory servers (dsn, log, cookies, session, secret, server….)

Yeah, doing my best between the self hosting docs on these config and just seeing what pulls from the GET config apis is my back up plan. But I'm hoping against hope that there's a doc that covers it more fully from an Ory Network perspective.

From my experience, you can use the keys not supported by Ory Network, and when using the CLI to update your tenant config, it will warn you of the keys that are discarded.

@steep-lamp-91158 any chance that something like this already exists? and/or is there any roadmap for some Ory Network docs around what config can/should be set to customize network instances?