-
Notifications
You must be signed in to change notification settings - Fork 18
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
ActiveRecord::RecordInvalid: Validation failed: Provider type translation missing: en.activerecord.errors.models.job_template.attributes.provider_type.uniq #120
Comments
How to reproduce: 🔴 Without Ansible:
🟢 With Ansible:
Not sure why it's happening, ansible is set as dependency, need to investigate closer .. |
Oh, that is interesting. I can confirm that $ bundle info foreman_ansible
* foreman_ansible (10.1.0) So it's also not pulling in an ancient version. Yet, when I add it to bundler it does load. That makes me think this code could be related: |
My theory is that bundler doesn't know to load the gem, somehow. If you list a gem in a gem 'foreman_ansible', require: false We have this code in Foreman to declare a dependency as well: Yet, I doubt its usefulness in the current form. One issue is the load order. If you first load Historical explanation why it makes sense to check the version: we have bundler_ext that discards the version checks that bundler does. However, we now also enforce the same dependencies via RPMs so that doesn't really make sense anymore. But something like this could be a path to ensure the dependency is actually loaded. The version matcher should be made optional (and deprecated) while also adding support for declaring an optional dependency. |
I've started hitting this in #133 too |
When trying to seed on a fresh installation I get:
The text was updated successfully, but these errors were encountered: