Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add ORY Kratos config schema to the catalog #1173

Merged
merged 1 commit into from
Aug 4, 2020

Conversation

zepatrik
Copy link
Contributor

@zepatrik zepatrik commented Aug 4, 2020

This PR adds the @ory Kratos config schema to the catalog. Please note that we automatically maintain the schema (ory/cli#13) to map the top level config key version to the corresponding schema on GitHub (as described in ory/kratos#608). This way we eliminate the need to determine the version as users specify it directly (similar to the kubernetes API version key).

@madskristensen madskristensen merged commit ec951c0 into SchemaStore:master Aug 4, 2020
@zepatrik zepatrik deleted the add-ory-kratos branch August 5, 2020 07:52
zepatrik added a commit to zepatrik/schemastore that referenced this pull request Aug 24, 2020
Analogously to SchemaStore#1173, this PR adds a reference to the version mapping schema on master of https://github.com/ory/hydra https://github.com/ory/oathkeeper and https://github.com/ory/keto.
Note that these mapper schemas are autogenerated on every release and therefore the current master always has all releases.
madskristensen pushed a commit that referenced this pull request Aug 24, 2020
Analogously to #1173, this PR adds a reference to the version mapping schema on master of https://github.com/ory/hydra https://github.com/ory/oathkeeper and https://github.com/ory/keto.
Note that these mapper schemas are autogenerated on every release and therefore the current master always has all releases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants