[Feature]: Generate AI endpoint configuration and launch shai CLI
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with internal/services/browser/api.go and internal/services/browser/manager.go, then locate the browser UI for AI endpoint actions. Trace how API credentials and endpoint details are handled before deciding how the action should detect and launch shai. Done means the listed acceptance criteria are covered, including loading, success, and missing-CLI error states.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues
Product concerned
Public cloud
Feature description
Add the ability to generate AI endpoint API credentials and configuration from the browser interface, then launch the shai CLI tool with the proper configuration for the selected endpoint.
Use Case
When browsing AI endpoints in the browser, users should be able to:
- Generate API credentials (API key) for that endpoint
- Automatically configure
shaiCLI with those credentials - Launch shai directly from the browser
This eliminates manual setup steps:
- Navigate to OVHcloud Manager
- Generate/copy API credentials
- Manually configure shai with credentials
- Launch shai separately
Acceptance Criteria
- Add "Launch shai" action when viewing AI endpoint details
- Generate API key for the selected endpoint (via API)
- Set up shai configuration with the generated credentials
- Graceful error handling if shai is not installed
- Show loading state during credential generation
- Display success message before launching shai
Implementation Details
- Call OVHcloud API to generate or fetch API key for the endpoint
- Create/update shai configuration file (typically
~/.config/shai/auth.config) - Set API key and endpoint URL in shai config
- Detect if shai CLI is installed before attempting launch
- Launch shai with proper access to the configured endpoint
- Provide helpful error messages if shai is missing or config invalid
Related Components
internal/services/browser/api.go- Add method to generate/fetch API keyinternal/services/browser/manager.go- Add action handler for launching shai- Browser UI - Add menu option for AI endpoint actions
- Dominant language
- Go
- Stars
- 217
- Forks
- 36
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 9
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from ovh/ovhcloud-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ovh/ovhcloud-cli#309 ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 1-2 days Newbie friendliness 48/100
ovh/ovhcloud-cli#303 ·
Maintainers usually reply within 3 days
-
[Feature]: Skill for this cliPossibly taken @duboolivier claimed this 63 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
ovh/ovhcloud-cli#207 ·
Maintainers usually reply within 3 days
-
[Feature]: Savings plan featureMay be free again @amstuta claimed this 117 days ago, and no pull request is open. Open
ovh/ovhcloud-cli#206 · 1 assignee ·
Maintainers usually reply within 3 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ovh/ovhcloud-cli#204 · 1 comment ·
Maintainers usually reply within 3 days
All issues in ovh/ovhcloud-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetone/magpie#4095 · 1 comment ·
Maintainers usually reply within 1 day
-
docs: Google Safe Browsing flags go-bonnie.dev as "deceptive" (pipe-to-shell install instructions)Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
[Bug]: Telegram bot (v3.11.0): "Ban log" no longer sends the current 3xipl-banned.logPossibly taken @HamedSanaei claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MHSanaei/3x-ui#6990 · 1 comment ·
Maintainers usually reply within 3 days
-
bug(tool/internal/instrument): identical inject_code rules from two rule packages are applied twiceOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-telemetry/opentelemetry-go-compile-instrumentation#1611 ·
Maintainers usually reply within 2 days