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

Remove problematic placeholder vars #734

Open
gotmax23 opened this issue Dec 2, 2023 · 2 comments
Open

Remove problematic placeholder vars #734

gotmax23 opened this issue Dec 2, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@gotmax23
Copy link

gotmax23 commented Dec 2, 2023

SUMMARY

The Python files and other code in ovirt.ovirt's git repository is syntactically invalid, as it uses placeholder values (@NAMESPACE@ and @NAME@) in the checked in code. This is disrupting efforts to test collections across the ansible package, as we cannot run ansible-test sanity without running extra scripts to preprocess the sources. Also, it prevents installing the collection straight from the git repository (ansible-galaxy collection install git+https://github.com/oVirt/ovirt-ansible-collection.git).

As far as I know, no other collections in the entire package, even the other ones that have different upstream/downstream collection names, do this. I would suggest using the upstream name in the source repository and then run a separate script to replace ovirt.ovirt across the collection with whatever the downstream name like the others do.

COMPONENT NAME

all

STEPS TO REPRODUCE

N/A

EXPECTED RESULTS

N/A

ACTUAL RESULTS

N/A

@gotmax23 gotmax23 added the bug Something isn't working label Dec 2, 2023
@mwperina
Copy link
Member

mwperina commented Dec 5, 2023

Hi @gotmax23 ,

placeholders in the collection were introduced due to inability to provide the same namespace used for upstream collection within Automation Hub as a fully supported collection by RH.
Before Automation Hub introduction oVirt Ansible modules were included within ansible 2.y distribution and oVirt Ansible roles were available in Galaxy and specific version were test and included in Red Hat Virtualization packaged as RPM, which mean that RHV customers could use any playbook tested on upstream and without any changes they could used it for RHV. Unfortunately when Automation Hub was introduced we needed to put oVirt Ansible Collection under redhat.rhv namespace, which completely broke our compatibility between upstream and downstream. So we were able to solve that within RHV RPMs, where we provide both namespaces.

And we definitely don't want to have 2 repositories, one for ovirt.ovirt and one for redhat.rhv, because that mean much more work and our resources are very limited.

Also we are running sanity tests as a part of our GH CI:
https://github.com/oVirt/ovirt-ansible-collection/blob/master/.github/workflows/build.yaml#L11

@mwperina
Copy link
Member

mwperina commented Dec 5, 2023

This was also discussed in #256 but without a resolution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants