Bug 1734630 - [RFE] set_stats - Support setting service_var from set_stats with naming convention
Summary: [RFE] set_stats - Support setting service_var from set_stats with naming conv...
Keywords:
Status: POST
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.12.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.12.0
Assignee: Lucy Fu
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-31 06:52 UTC by Loic Avenel
Modified: 2019-12-17 17:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)

Description Loic Avenel 2019-07-31 06:52:48 UTC
[RFE] set_stats - Support setting service_var from set_stats with naming convention

Comment 2 Tina Fitzgerald 2019-10-31 18:29:22 UTC
Hi Lucy,

Using set_stats in a playbook:

set_stats value: service_var__var1

1. Sets the ansible_stat state var is currently supports.
2. Create/Updates a service_var with the name of ansible_stat_var1

Let me know if you have any questions.

Thanks,
Tina

Comment 4 CFME Bot 2019-12-17 15:31:58 UTC
New commit detected on ManageIQ/manageiq-automation_engine/master:

https://github.com/ManageIQ/manageiq-automation_engine/commit/bc3d8a38842653add6575f2d639a5763bafc115a
commit bc3d8a38842653add6575f2d639a5763bafc115a
Author:     Lucy Fu <lufu@redhat.com>
AuthorDate: Thu Oct 24 15:06:06 2019 -0400
Commit:     Lucy Fu <lufu@redhat.com>
CommitDate: Thu Oct 24 15:06:06 2019 -0400

    Update service_vars from playbook set_stats data.

    https://bugzilla.redhat.com/show_bug.cgi?id=1734630

 lib/miq_automation_engine/engine/miq_ae_engine/miq_ae_ansible_method_base.rb | 20 +
 spec/miq_ae_playbook_method_spec.rb | 10 +-
 2 files changed, 29 insertions(+), 1 deletion(-)


Note You need to log in before you can comment on or make changes to this bug.