Remove the tripleo.plan_management.v1.publish_ui_logs_to_swiftworkflow

This was only used by tripleo-ui and is no longer needed.

Related-bug: #1835242
Depends-On: https://review.opendev.org/#/c/669159/
Change-Id: I0419ca070553ad7261cda947c2d246a44df5580d
This commit is contained in:
Dougal Matthews 2019-07-04 13:23:31 +01:00
parent a2fef2af3b
commit 29ef322d96
1 changed files with 0 additions and 60 deletions

View File

@ -723,66 +723,6 @@ workflows:
execution: <% execution() %>
plan_name: <% $.container %>
publish_ui_logs_to_swift:
description: >
This workflow drains a zaqar queue, and publish its messages into a log
file in swift. This workflow is called by cron trigger.
input:
- logging_queue_name: tripleo-ui-logging
- logging_container: tripleo-ui-logs
tags:
- tripleo-common-managed
tasks:
# We're using a NoOp action to start the workflow. The recursive nature
# of the workflow means that Mistral will refuse to execute it because it
# doesn't know where to begin.
start:
on-success: get_messages
get_messages:
action: zaqar.claim_messages
on-success:
- format_messages: <% task().result.len() > 0 %>
input:
queue_name: <% $.logging_queue_name %>
ttl: 60
grace: 60
publish:
status: SUCCESS
messages: <% task().result %>
message_ids: <% task().result.select($.id) %>
format_messages:
action: tripleo.logging_to_swift.format_messages
on-success: upload_to_swift
input:
messages: <% $.messages %>
publish:
status: SUCCESS
formatted_messages: <% task().result %>
upload_to_swift:
action: tripleo.logging_to_swift.publish_ui_log_to_swift
on-success: delete_messages
input:
logging_data: <% $.formatted_messages %>
logging_container: <% $.logging_container %>
publish:
status: SUCCESS
delete_messages:
action: zaqar.delete_messages
on-success: get_messages
input:
queue_name: <% $.logging_queue_name %>
messages: <% $.message_ids %>
publish:
status: SUCCESS
list_roles:
description: Retrieve the roles_data.yaml and return a usable object