Make Landscape tags available to scripts within Landscape-Client

Bug #2003362 reported by Chris Hill
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Confirmed
Wishlist
Unassigned

Bug Description

Not sure if this is the place for feature requests but...

At present it is possible to assign 'tags' to computers, which is really helpful for managing computers within the Landscape Server console. For example, it can be used to tag computers which carry out particular roles etc.

It would be helpful for scripting and automation to make these 'tags' available to read on the computers themselves:

Either
a) (Preferable) In the form of file(s) written and updated to /var/lib/landscape/client or similar (so that you could check if a file exists - if so, the machine has that tag) - this would mean it could be read by any process running on the device.
b) (Less useful) A new environment variable in the form of an array which can be added to Landscape Scripts as they are run.

I am aware of annotations, but I think these only allow data to be sent from client -> server, but not the other way? Also, the --tags parameter in landscape-config allows tags to be sent from client -> server during initial registration, but there doesn't appear to be support for server -> client - updating tags on the server side does not update /etc/landscape/client.conf.

Looking forward to what is possible here!

Changed in landscape-client:
importance: Undecided → Wishlist
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.