No Provider of openSUSE-release Found

I’m getting this error while installing rpmdevtools from PackageHub/15/x86_64:
No provider of ‘openSUSE-release’ found.
I am installing into a docker container of SLES15. The container is registered to the server and I have added sle-module-desktop-applications/15/x86_64, sle-module-development-tools/15/x86_64 and PackageHub/15/x86_64 through SUSEConnect.
I don’t see this package in anywhere. Only related packages are listed (openSUSE-release-tools, etc…). I only need this to pass dependency check for

Should I be adding the repo externally? The suggested repos are 404-ing (From
e.g. zypper addrepo

So is this container running openSUSE Leap 15.2 (which is beta?)?

The container is running SLES15 SP0 and I have similar issues with SP1 containers. I realized the issue is during container creation, zypper is requesting input during the docker build command and non-interactive mode defaults aren’t what I want. There doesn’t seem to be a way to override this decision in automation. Piping anything to stdin is ignored when zypper gets to the below prompt. Can’t find a setting in /etc/zypp/zypp.conf.

 Problem: nothing provides openSUSE-release needed by rpmdevtools-8.10-bp150.2.4.noarch
 Solution 1: do not install rpmdevtools-8.10-bp150.2.4.noarch
 Solution 2: break rpmdevtools-8.10-bp150.2.4.noarch by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c/d/?] (c):  c

I don’t care to install openSUSE-release so I am ok with solution 2. However, on SLES 15 SP1 container it’s even worse, it can’t find rpm-python package.

Problem: nothing provides rpm-python needed by rpmdevtools-8.10-bp151.4.3.1.noarch
 Solution 1: do not install rpmdevtools-8.10-bp151.4.3.1.noarch
 Solution 2: break rpmdevtools-8.10-bp151.4.3.1.noarch by ignoring some of its dependencies

Got it working, with installing rpmdevtools through zypper from opensuse directly from a different repo:

I did ping one of my SUSE Package Hub contacts, it is a bug and was thought to be fixed. Looks like you have a workaround, but when fixed should sort it out after an update.