Init process of using embargoed field for Incidents

[asmorodskyi]

Because of usage of same data structures in two independent applications (qem-bot and qem-dashboard)
we need to do introduction of new field in several stages. At first stage we will start pushing
this field into qem-dashboard from qem-bot. So after deploying this we can than read propely
this field coming from bot

[Martchus]

Looks like tests still need to be adapted.

[kraih]

Very useful test failures, confirm that it actually works as expected. Actually looks like the wrong place, what you want is the incident metadata, not the openQA jobs (probably PATCH /api/incidents).

[kraih]

Looks like the wrong place. It should be incidents and not openQA jobs.

[asmorodskyi]

Looks like the wrong place. It should be incidents and not openQA jobs.

yes you are correct . Is it right place now ?

Updated

[asmorodskyi]

sorry not fully aware about workflows used in this project , so please don't get this as me trying to push you . But if there anything on me that is blocking this PR to be merged ?

[okurz]

sorry not fully aware about workflows used in this project , so please don't get this as me trying to push you . But if there anything on me that is blocking this PR to be merged ?

Nothing needs to be done by you. This just needs at least a second person reviewing and approving this PR whenever they find their github pull request review time. As the last update was on Friday and we are just in the middle of the next usual business day, i.e. Monday, I wouldn't be concerned.

[kraih]

Does look like the right place.