The taggable methods for service models are defined in
MiqAeServiceModelBase, which would imply they they are relevant to all service models. I’ve recently noticed however that this isn’t necessarily the case; several of the /app/models that the service models map to don’t include
acts_as_miq_taggable, so do not support tagging (the Lan/MiqAeServiceLan pairing being an example). If we try to access the
tags method of such a service model object for example we get an exception:
NoMethodError: undefined method tag_list for #<Lan:0x00000008e936c8>
So a bit of an architectural question, what would be the downside of making all models taggable? Even of we didn’t expose this in the WebUI, it’s fantastically useful to be able to apply and read tags to/from an object from automate.