This repository has been archived by the owner on May 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 41
Model blows up when accessing a new attribute not seen by initializer #95
Labels
Comments
jameswnl
pushed a commit
to jameswnl/ansible_tower_client_ruby
that referenced
this issue
Jul 11, 2017
jameswnl
pushed a commit
to jameswnl/ansible_tower_client_ruby
that referenced
this issue
Jul 11, 2017
jameswnl
pushed a commit
to jameswnl/ansible_tower_client_ruby
that referenced
this issue
Jul 11, 2017
jameswnl
pushed a commit
to jameswnl/ansible_tower_client_ruby
that referenced
this issue
Jul 11, 2017
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation. |
This issue has been automatically closed because it has not been updated for at least 3 months. Feel free to reopen this issue if this issue is still valid. Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Attribute accessors are only created by initializers (right?). If we try to access a legitimate attribute (i.e. from Ansible Tower perspective) but hasn't been seen by initializer yet, it will blow up.
This is breaking https://travis-ci.org/ManageIQ/manageiq-providers-ansible_tower/jobs/250498451#L868.
Seems to me the simplest solution is to have
method_missing
defined to handle this.@bdunne @syncrou what do you think?
This is related to #68.
The text was updated successfully, but these errors were encountered: