maybe that is something others would like, too:
Is it possible (in a future version of service catalog / pinakes) that the information (username, mail address) of the logged in user in service catalog to be transferred as extra-vars to the controller job template? Maybe as some default/preconfigured variables names. So that it is possible to work with the information of the requested user that ordered the service in the playbook. Some examples that can be done with this information:
create a ticket in a ticket tool and add the user as the affected user in the ticket and add information about the controller job
send the user an email when the playbook is finished
for playbooks that do renaming of user properties (like address, telephone number)
The only workaround is currently to let the user enter his login during the survey in service catalog or?
Hi,
maybe that is something others would like, too: Is it possible (in a future version of service catalog / pinakes) that the information (username, mail address) of the logged in user in service catalog to be transferred as extra-vars to the controller job template? Maybe as some default/preconfigured variables names. So that it is possible to work with the information of the requested user that ordered the service in the playbook. Some examples that can be done with this information:
The only workaround is currently to let the user enter his login during the survey in service catalog or?
Regards, Stephan