-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R4
-
Component/s: API
-
Labels:
-
Sprint:CFAMX 2020R4 Sprint 3
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:8
-
Work Type Classification:Sustaining
As a developer, I want the new API stack to be part of the Build and Deploy processes. This requires a few steps:
1) New Step added to Build
2) Results of that Build added to a a ZIP file
3) Deploy process updated to deploy new API stack
3a) also remove failing, empty Slices deploy
4) Begin process of new IPs, DNS entries, SSL and future deploy level environment setup
- implements
-
CFAMX-10366 Make the Waste API robust enough for chain-wide usage by Automated Holding Assistant to inject waste data
-
- Closed
-
1.
|
Test Deploy |
|
Done | Soma Dixon (Inactive) |
|
||||||||
2.
|
Deploy |
|
Done | Unassigned |
|
||||||||
3.
|
Functional Review with QA |
|
Done | Unassigned |
|
||||||||
4.
|
DIT |
|
Done | Unassigned |
|
||||||||
5.
|
Add Build steps to compile and package |
|
Done | Michael DeBinder (Inactive) |
|
||||||||
6.
|
Update Deploy to copy new package to correct folder |
|
Done | Michael DeBinder (Inactive) |
|
||||||||
7.
|
Begin Discussion with ops about new setup |
|
Done | Michael DeBinder (Inactive) |
|
