Support Suse enterprise repository

[h-haaks]

Pull Request (PR) description

Adding support for Suse enterprise repository

[h-haaks]

We don't have tesing on Suse but the enterprise repo is there so I guess it's ok to add it.

[h-haaks]

Should we add opensuse to metadata to get it tested?

[stevenpost]

I would like to see these moved to module data, so code gets a lot simpler, I was thinking of having 2 parameters, 1 for the community edition and one for the enterprise edition.

That can go in a follow-up PR.

[h-haaks]

Should we add opensuse to metadata to get it tested?

Tried to run beaker with opensuse15-64 and docker but it seems like beaker-docker is still using the old and deprecated amd64/opensuse/leap images ...

[h-haaks]

I would like to see these moved to module data, so code gets a lot simpler, I was thinking of having 2 parameters, 1 for the community edition and one for the enterprise edition.

Do you mean two repo location params? Thats a bit odd if the class should only manage one repo.

[stevenpost]

I would like to see these moved to module data, so code gets a lot simpler, I was thinking of having 2 parameters, 1 for the community edition and one for the enterprise edition.

Do you mean two repo location params? Thats a bit odd if the class should only manage one repo.

Yes, then the code can do something like:

$_real_repo = $use_enterprise_repo ? {
  true    => $community_repo,
  default => $enterprise_repo,
}

If going with a single parameter, it needs to be undef by default and we end up with a huge select for the OS as well.