Updates/ory api

[mfreeman451]

Summary by CodeRabbit

Release Notes

• Bug Fixes

  • Removed deprecated configuration files and entries that could affect application deployment and performance.

• New Features

  • Introduced new API routes for managing API credentials, enhancing functionality for user authentication and authorization.

• Documentation

  • Updated authentication flow documentation for clarity and comprehensiveness.

• Chores

  • Updated Kubernetes configurations to streamline deployment processes and improve overall application management.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request involves the deletion of several files related to the api-admin component, including configuration files, Dockerfiles, and Kubernetes resources. The removed files include build configurations, environment variable settings, and deployment specifications, which collectively eliminate the operational setup for the api-admin service. Additionally, modifications are made to the main.go file for the api component, introducing new API routes and altering the handling of OAuth2 client configurations. The changes also include updates to environment variables and service configurations in other components.

Changes

File Path	Change Summary
cmd/api-admin/.ko.yaml	Removed configuration settings for api-admin build process, including base image and platform details.
cmd/api-admin/Dockerfile	Deleted multi-stage Dockerfile for containerized application setup.
cmd/api-admin/Makefile	Removed build instructions for the api-admin project.
cmd/api-admin/configs/.env	Deleted environment variable configuration file for api-admin.
cmd/api-admin/main.go	Deleted main entry point for api-admin, which included web application initialization and API routes.
cmd/api-admin/superuser.json	Removed JSON file containing superuser email address.
k8s/api-admin/base/api-admin.yaml	Deleted Kubernetes Deployment configuration for api-admin.
k8s/api-admin/base/configmap.yaml	Removed Kubernetes ConfigMap for api-admin configuration settings.
k8s/api-admin/base/db-creds.yaml	Deleted Kubernetes Secret resource for database credentials.
k8s/api-admin/base/health-alive-ingress.yaml	Removed two Kubernetes Ingress resources for health checks.
k8s/api-admin/base/ingress-api.yaml	Deleted Ingress resource for routing HTTP traffic to api-admin.
k8s/api-admin/base/ingress-callback.yaml	Removed Ingress resource for routing callback traffic.
k8s/api-admin/base/ingress.yaml	Deleted Ingress resource for api-admin service.
k8s/api-admin/base/kustomization.yaml	Removed Kustomization configuration file for managing Kubernetes resources.
k8s/api-admin/base/service-proxy.yaml	Deleted Kubernetes Service resource for oathkeeper-proxy.
k8s/api-admin/base/service.yaml	Removed Kubernetes Service resource for api-admin.
k8s/api/base/api.yaml	Updated image version for api application deployment.
k8s/hydra/values.yaml	Modified Hydra service configuration, including allowed claims and environment variables.
k8s/oathkeeper/values.yaml	Updated Oathkeeper configuration, including URL and header adjustments.
pkg/api/handlers/api_credentials.go	Enhanced logging and modified OAuth2 client configuration in CreateAPICredential function.
pkg/api/handlers/handlers.go	Updated UserInfo struct to support multiple roles and modified role checking logic.
pkg/api/middleware/rbac.go	Adjusted casing of claim keys in RequireUser middleware and GetAuthClaims function.
docs/auth.md	Enhanced documentation with new flow diagrams for authentication processes.

Possibly related PRs

• Updates/use gofr oauth #37: Updates to the OAuth configuration, related to API management and authentication.
• 🔧 WIP ory crap #39: Modifies authentication rules in a ConfigMap, relevant to the configuration of the api-admin service.
• Updates/use gofr oauth #40: Updates oathkeeper-rules ConfigMap, directly related to authentication and authorization mechanisms.
• 🔧 sync #42: Enhances documentation for the Auth Server, connected to API administration changes.
• sync #44: Modifies oathkeeper-rules-data ConfigMap, relevant to operational parameters of the API.

🐇 In the burrow, changes abound,
The api-admin files no longer found.
With routes anew and configs erased,
A lighter path for our code is traced.
Hops of progress, swift and bright,
In the code garden, all feels right! 🌱

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint (1.61.0)

level=error msg="Running error: context loading failed: failed to load packages: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: go: cannot load module ../gofr listed in go.work file: open ../gofr/go.mod: no such file or directory\n"

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.