-
Story
-
Resolution: Done
-
Major
-
Global Hub 1.6.0
-
Product / Portfolio Work
-
2
-
False
-
-
False
-
-
-
-
GH Train-31
-
Important
-
None
Value Statement
As a platform admin running migrations,
I want to customize the timeout duration of each migration stage using annotations,
So that I can better control how long each stage should wait before failing, depending on my environment.
Definition of Done for Engineering Story Owner (Checklist)
User could config the stage timeout by:
// code placeholder
supportedConfigs:
stageTimeout: 10m
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- clones
-
ACM-22900 As cluster admin, I can run migration process without a database dependency
-
- New
-