Looks like you can't configure all of the Ory Netw...
# ory-network
b
Looks like you can't configure all of the Ory Network via the CLI, so this isn't a valid option for me
m
what is missing for you?
b
I'll have to go through all my logs, but there were many sections of the config that came up as a warning that they couldn't be updated via the cli.
The cookie path, domain, session.cookie.domain etc are pretty critical
Copy code
Warnings were found.
- Configuration key `serve.*` can not be set and will be ignored.
- Configuration key `cookies.path` can not be set and will be ignored.
- Configuration key `cookies.domain` can not be set and will be ignored.
- Configuration key `session.cookie.domain` can not be set and will be ignored.
- Configuration key `session.cookie.name` can not be set and will be ignored.
- Configuration key `session.cookie.path` can not be set and will be ignored.
- Configuration key `clients.http.disallow_private_ip_ranges` can not be set and will be ignored.
- Configuration key `clients.http.private_ip_exception_urls` can not be set and will be ignored.
- Configuration key `clients.smtp.disallow_private_ip_ranges` can not be set and will be ignored.
- Configuration key `clients.web_hook.header_allowlist` can not be set and will be ignored.
- Configuration key `serve.public.tls.*` can not be set and will be ignored.
- Configuration key `serve.admin.tls.*` can not be set and will be ignored.
- Configuration key `serve.tls` can not be set and will be ignored.
- Configuration key `serve.cookies.domain` can not be set and will be ignored.
- Configuration key `serve.cookies.names.*` can not be set and will be ignored.
- Configuration key `clients.http.disallow_private_ip_ranges` can not be set and will be ignored.
- Configuration key `clients.http.private_ip_exception_urls` can not be set and will be ignored.
- Configuration key `oauth2.expose_internal_errors` can not be set and will be ignored.
- Configuration key `oauth2.session.encrypt_at_rest` can not be set and will be ignored.
- Configuration key `oauth2.hashers.*` can not be set and will be ignored.
- Configuration key `hsm.*` can not be set and will be ignored.
- Configuration key `urls.self.public` can not be set and will be ignored.
- Configuration key `urls.self.admin` can not be set and will be ignored.
It is safe to ignore these warnings unless your intention was to set these keys.

Project updated successfully!

Failing: --strict and Ory reported warnings.
failed to wait for command termination: exit status 1
m
Yea I think the only thing that is not settable via the CLI is the custom domain. I'll check to confirm.
b
Is that available in the terraform provider?
m
No, since the terraform provider and the CLI all use the same /project API. You can configure identity/Kratos (schemas, self-service methods, courier/SMTP, sessions), OAuth2/Hydra (TTLs, PKCE, OIDC, client defaults), Keto permission namespaces, Account Experience theming, CORS origins, and CRUD for projects, workspaces, organizations, and event streams. Custom domains, access control (members/API keys), and billing are Console-only at the moment. I think it would make sense to add custom domain stuff as well - found an open issue here: github.com/ory/cli/issues/356 If you feel like it add some details of your use case to that issue. That would help me when talking to the product team about it.
b
that's a bit annoying, I've updated the ticket, but the original one is pretty one point. I won't hold my breath as its been open for 2 years!
m
Yea I don't expect it to be solved immediately but I think the issue got also kind stale since there wasn't much interest from other users in that feature. You commenting and describing the use case helps a lot. I will bring it up with the product team and see where it sits for them. Thanks again for the feedback 🙏