Cannot patch my Ory Network project with a config-file using the Ory CLI
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 96
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Network project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe the bug
I'm trying to use the Ory CLI to patch my project with a configuration file.
This results in the following error message:
json: cannot unmarshal object into Go value of type []client.JsonPatch
The file I'm feeding into the command is also retrieved using the CLI.
I'm running the following commands:
ory get project <redacted> --format json > config.json
ory patch project <redacted> --file file://config.json
Reproducing the bug
ory get project <redacted> --format json > config.json
ory patch project <redacted> --file file://config.json
Relevant log output
json: cannot unmarshal object into Go value of type []client.JsonPatch
Relevant configuration
No response
Version
Ory Network
On which operating system are you observing this issue?
Ory Network
In which environment are you deploying?
Ory Network
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two documented commands: retrieve a project with ory get project --format json, then pass that file to ory patch project --file file://config.json. Read the Ory CLI handling for the --file argument and the project patch request shape, and compare it with the retrieved JSON. Done means a retrieved configuration can be used successfully for the documented patch operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100