Skip to content

feat: Configure Permission Service using CLI guide #864

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

Merged
merged 1 commit into from
Jun 15, 2022

Conversation

zepatrik
Copy link
Member

@@ -1,6 +1,7 @@
---
id: cli-basics
title: Basic Functionality
sidebar_position: 5
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing file content is better to review than changing file names IMO. I can also revert this, but we did not use the number convention elsewhere so this is also more consistent.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing filenames broke two relative links which causes the website build to fail. Logs:

Error: Docs markdown link couldn't be resolved: (../guides/cli/10_config-with-cli.mdx) in /docs/docs/concepts/personal-access-token.mdx for version current
    at Array.forEach (<anonymous>)
Error: Docs markdown link couldn't be resolved: (./cli/20_proxy-and-tunnel.mdx) in /docs/docs/guides/custom-domains.mdx for version current
    at Array.forEach (<anonymous>)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The system where the document order is determined by filenames is something I'm trying out and I really like it so far. The benefits are:

  • the sidebars file is leaner
  • you can see the correlation between the left navigation and the files in the directory at the first glance
  • when you start messing with the file order you don't have to open any other files to know what to do - everything is visible at a glance without having to inspect the metadata section of the docs

I'm slowly implementing this system as I update/refactor/create new documents. For know, I think that this is the way to go.

Please revert filenames to their initial state. This will fix your failing build.

@@ -54,7 +55,7 @@ ory get identity-config <project-id> --format yaml > identity-config.yaml

## Import Configuration to Ory Cloud

To start using using the configuration from a self-hosted Ory Kratos instance in the Ory Cloud Identity Service, import the
To start using the configuration from a self-hosted Ory Kratos instance in the Ory Cloud Identity Service, import the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙆🏻

Copy link
Contributor

@tomekpapiernik tomekpapiernik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The document you added looks okay - it's basically the same as the Identity Service.
Please revert back to the old file naming structure to fix the builds and make your TW happy.

@zepatrik zepatrik force-pushed the feat/permission-config branch from ee9f840 to f81561e Compare June 14, 2022 11:56
@zepatrik zepatrik merged commit 89fd19d into master Jun 15, 2022
@zepatrik zepatrik deleted the feat/permission-config branch June 15, 2022 07:34
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