Add "published_global" field to the task execution REST resource
Bug #1751007 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Eyal B |
Bug Description
We now expose "published" that contains all variables published into the branch local storage. Some time ago we added publishing to the workflow global storage. So we need a corresponding field on the REST resource.
Changed in mistral: | |
milestone: | none → rocky-1 |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
Changed in mistral: | |
milestone: | rocky-1 → rocky-2 |
status: | Confirmed → Triaged |
Changed in mistral: | |
milestone: | rocky-2 → rocky-3 |
status: | Triaged → Confirmed |
Changed in mistral: | |
milestone: | rocky-3 → stein-1 |
Changed in mistral: | |
milestone: | stein-1 → stein-2 |
Changed in mistral: | |
milestone: | stein-2 → stein-3 |
Changed in mistral: | |
milestone: | stein-3 → train-1 |
summary: |
- Add "published_global" field to the workflow execution REST resource + Add "published_global" field to the task execution REST resource |
Changed in mistral: | |
assignee: | Renat Akhmerov (rakhmerov) → Eyal B (eyalb1) |
Changed in mistral: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Will be good to add some field to support both "publish" and "advanced publish" for all scopes so customers can switch to the new field and completely ignore the old one ("advanced_ published" as a temporary name).
For example:
wf:
tasks:
A:
action: std.noop
publish:
my_var: 1
will have "advanced_ published" like:
branch:
my_var: 1
Another example:
wf:
counter: <% global(counter) + 1 %>
tasks:
A:
action: std.noop
on-success:
publish:
branch:
my_var: "branch value"
global:
my_var: "global value"
atomic:
will have "advanced_ published" like:
branch:
my_var: "branch value"
global:
my_var: "global value"
atomic: