You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I need a public API call (that works regardless of build service instance) that returns the generated contents of a .repo file. My understanding is that the backend is able to create this and write it out, as it does on the openSUSE Build Service, but there's no instance-agnostic way to just get the contents of said file to curl and write to disk.
Since there is a high degree of variation of where the repo content actually could be (either on port 82 of the same address, as private instances are by default, or on a separate system like openSUSE's is, or whatnot), an API means that the plugin won't be brittle and will be able to work with public and private OBS instances alike.
The text was updated successfully, but these errors were encountered:
I'd also greatly appreciate it if this was also made available in OBS 2.8 as a backport, so that relatively new private instances can leverage the plugin, too.
Feature description
I am working on implementing a plugin for the DNF package manager (the successor to Yum) for managing OBS repos (see rpm-software-management/dnf-plugins-extras#64).
However, I need a public API call (that works regardless of build service instance) that returns the generated contents of a .repo file. My understanding is that the backend is able to create this and write it out, as it does on the openSUSE Build Service, but there's no instance-agnostic way to just get the contents of said file to curl and write to disk.
Since there is a high degree of variation of where the repo content actually could be (either on port 82 of the same address, as private instances are by default, or on a separate system like openSUSE's is, or whatnot), an API means that the plugin won't be brittle and will be able to work with public and private OBS instances alike.
The text was updated successfully, but these errors were encountered: