* feat: auth remove: add -b flag
Signed-off-by: Pavel Sturc <psturc@redhat.com>
* fix: address comment
Signed-off-by: Pavel Sturc <psturc@redhat.com>
---------
Signed-off-by: Pavel Sturc <psturc@redhat.com>
Co-authored-by: Alex Jones <alexsimonjones@gmail.com>
* add amazonbedrock AI provider
Signed-off-by: Su Wei <suwei007@gmail.com>
* add amazonbedrock, change model list to const var
Signed-off-by: Su Wei <suwei007@gmail.com>
* update iai config and auth cmd, add providerRegion
Signed-off-by: Wei Su <wsuam@amazon.com>
* fix filename wrong
Signed-off-by: Wei Su <wsuam@amazon.com>
* chore: added some doc info
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
---------
Signed-off-by: Su Wei <suwei007@gmail.com>
Signed-off-by: Wei Su <wsuam@amazon.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Co-authored-by: Wei Su <wsuam@amazon.com>
Co-authored-by: Aris Boutselis <aris.boutselis@senseon.io>
Co-authored-by: Alex Jones <alexsimonjones@gmail.com>
The `auth add` cmd should use `backend` and `model` default values when user doesn't specify them
Closes: #567
Signed-off-by: Jian Zhang <jiazha@redhat.com>
Co-authored-by: Thomas Schuetz <38893055+thschue@users.noreply.github.com>
Co-authored-by: Alex Jones <alexsimonjones@gmail.com>
* feat: openAI explicit value for maxToken and temp
Because when k8sgpt talks with vLLM, the default MaxToken is 16,
which is so small.
Given the most model supports 2048 token(like Llama1 ..etc), so
put here for a safe value.
Signed-off-by: Peter Pan <Peter.Pan@daocloud.io>
* feat: make temperature a flag
Signed-off-by: Peter Pan <Peter.Pan@daocloud.io>
---------
Signed-off-by: Peter Pan <Peter.Pan@daocloud.io>
* feat: added the ability to set a user default AI provider
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* feat: added the ability to set a user default AI provider
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* feat: s3 based caching
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* feat: s3 based caching
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* updated README.md
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* update README.md
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* updated README.md
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* chore: region is a must have
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* chore: clarified remove command
* updated remove.go
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* chore: test fmt causing issues will open another pr
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
---------
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* feat: rename "auth new" to "auth add"
This change allows to be more consistent with the rest of the code
Signed-off-by: Matthis Holleville <matthish29@gmail.com>
* feat: rework "auth remove" to be more consistent with other remove commands like "filters remove"
Signed-off-by: Matthis Holleville <matthish29@gmail.com>
* feat: update documentation
Signed-off-by: Matthis Holleville <matthish29@gmail.com>
---------
Signed-off-by: Matthis Holleville <matthish29@gmail.com>
* feat: added the ability to set a user default AI provider
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* feat: added the ability to set a user default AI provider
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* chore: added provider to json output
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
---------
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
* feat: allow to set a baseURL for OpenAI providers
This allows to run local models that have a compatible OpenAI API, or
for instance use a proxy.
Signed-off-by: mudler <mudler@mocaccino.org>
* feat: allow to set baseURL in the auth subcommand
Signed-off-by: mudler <mudler@mocaccino.org>
---------
Signed-off-by: mudler <mudler@mocaccino.org>
Co-authored-by: Alex Jones <alexsimonjones@gmail.com>
Co-authored-by: Matthis <99146727+matthisholleville@users.noreply.github.com>
This commit adds support for a new configuration format that is not backwards compatible with the previous format. This is a breaking change and requires users to update their configuration files to use the new format.
BREAKING CHANGE: The format of the configuration file has changed. Users must update their configuration files to use the new format.
Signed-off-by: Matthis Holleville <matthish29@gmail.com>
