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

[TerminalChat/AI; Enterprise] Company wide predefine lm provider parameter #18159

Open
htcfreek opened this issue Nov 6, 2024 · 0 comments
Open
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@htcfreek
Copy link

htcfreek commented Nov 6, 2024

Description of the new feature

Add a second group policy to set the required ChatAI/LM provider parameters like endpoint uri, api key, and so on.

Use case

That a company can push the configuration to their clients instead of telling (mail or documentation) their users how to configure the provider. This is especially useful if all people should use the same (local/on premise) LM provider infrastructure.

Implementation notes

  • String policy accepting a json value in one line.
  • Maybe not possible because of the encryption of the api key(s).
  • Maybe a second policy for the provider that is enabled by default.
  • Possible json format:
{
  "defaultEnabledProvider": "lm-provider-id",
  "lm-provider-id": [
    "property": "value",
    "property": "value"
  ],
  "lm-provider-id2": [
    "property": "value",
    "property": "value"
  ]
}

Proposed technical implementation details

No response

@htcfreek htcfreek added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 6, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

1 participant