-
Notifications
You must be signed in to change notification settings - Fork 18
AttributeError: 'RequirementSpec' object has no attribute 'scm' #236
Comments
The current version of mazer doesn't support install traditional roles (like 'direct install of traditional roles' meaning things like this aren't expected to work
But install of collections from galaxy is supported (though not from production galaxy.ansible.com quite yet) and meant to work:
'alikins-collection_ntp-1.2.3.tar.gz' is the collection 'artifact' built as result of running 'mazer build' in a checkout of https://github.com/alikins/collection_ntp
At the moment, collection installs from an scm_url don't quite work correctly either. I'm working on getting scm url installs of collections working again, but the scm url and install code paths need some changes to deal with the way scm urls aren't necessarily versioned. For example, if 'git+https://github.com/alikins/my_collection' was installed to satisfy a requirement for 'alikins.my_collection >= 2.0.0', https://github.com/alikins/my_collection may not have any versioning info, so it's hard to tell if the 'requirement' was solved. The traceback is definitely a bug, but for that usage there will still be an error since 'ansible-role-nginx' is a role and not a 'collection', and mazer now only supports installing collections (but that is also broken at moment) |
Previously it was 'req_spec_string' to distinquish from RepositorySpec, but RepoSpec and ReqSpec are separated now, so just use 'spec_string' for both as that is what the repo spec parsing code does. Add 'scm' attribute back to RequirementSpec. Fixes part of ansible#236 Fixes "AttributeError: 'RequirementSpec' object has no attribute 'scm'" error on 'mazer install git+https://github.com/alikins/whatever' (collection install still fails, but for a different reason)
Previously it was 'req_spec_string' to distinquish from RepositorySpec, but RepoSpec and ReqSpec are separated now, so just use 'spec_string' for both as that is what the repo spec parsing code does. Add 'scm' attribute back to RequirementSpec. Fixes part of ansible#236 Fixes "AttributeError: 'RequirementSpec' object has no attribute 'scm'" error on 'mazer install git+https://github.com/alikins/whatever' (collection install still fails, but for a different reason)
Previously it was 'req_spec_string' to distinquish from RepositorySpec, but RepoSpec and ReqSpec are separated now, so just use 'spec_string' for both as that is what the repo spec parsing code does. Add 'scm' attribute back to RequirementSpec. Fixes part of #236 Fixes "AttributeError: 'RequirementSpec' object has no attribute 'scm'" error on 'mazer install git+https://github.com/alikins/whatever' (collection install still fails, but for a different reason)
Bug Report
MAZER VERSION
Ansible:
CONFIGURATION
default
SUMMARY
Fail to install role from github.
STEPS TO REPRODUCE
EXPECTED RESULTS
Expect to not get an error
ACTUAL RESULTS
Error:
The text was updated successfully, but these errors were encountered: