action #27076
closed
[tools][functional][hard] Add functionality to be able to modify data available via http in share directory
Added by riafarov over 6 years ago.
Updated over 6 years ago.
Category:
Feature requests
Description
User story¶
As a test developer I would like to modify files we share in data test directory during the test run. One of valid scenarios is modification of autoyast profiles from the worker side avoiding need in support server.
At the moment it's only possible to modify profiles that can be used for installation only using support server, which has certain limitations.
For example, it's not straight-forward to share the path to the new file between 2 test suites, if modification was done in support server test suite.
Another possibility to have similarly functionality atm is to use 'upload_asset', here we can avoid having support server, but still have to run code inside of SUT in chained job.
acceptance criteria¶
- AC1: Being able to modify and upload files similarly to 'upload_asset' but not from SUT, but from the worker directly
- AC2: Being able to access files in SUT using http
tasks¶
- Investigate required steps
- Implement new api function which allows uploading files
- Document new api function
- Related to action #23736: [sle][functional] Adjust autoinst profiles for sle 15 added
- Related to deleted (action #23736: [sle][functional] Adjust autoinst profiles for sle 15)
- Blocks action #23736: [sle][functional] Adjust autoinst profiles for sle 15 added
- Blocks deleted (action #23736: [sle][functional] Adjust autoinst profiles for sle 15)
- Blocks action #27505: [sle][functional][y][autoyast][fast] Modify autoyast profiles during the run added
- Description updated (diff)
- Blocks action #28349: [sle][functional] Use registration in autoinst profiles for sle 15 added
- Subject changed from [tools] Add functionality to be able to modify data available via http in share directory to [tools][functional] Add functionality to be able to modify data available via http in share directory
- Due date set to 2017-12-19
- Target version set to Milestone 12
that's very relevant for "functional". Let's try something different and make this issue "explicit" on the functional backlog and plan for our sprint6 then
- Status changed from New to In Progress
- Subject changed from [tools][functional] Add functionality to be able to modify data available via http in share directory to [tools][functional][hard] Add functionality to be able to modify data available via http in share directory
- Status changed from In Progress to Resolved
PR merged, we need to wait until changes are deployed to the o3 and osd before starting using this functionality.
Also available in: Atom
PDF