Overrides/Supersedes
This decision was migrated from the Tech Leads Decision Log as part of a consolidation process. The original decision record can be found here.
RFC
N/A
Stakeholders
- All developers, SysOps, Hosting providers
Contributors
Approvers
This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.
Background/Context
One pain point identified during the Iris bugfest retrospective was that some modules have specific deployment requirements which were essentially undocumented. A few examples include:
- Environment variables and Java options
- Secrets that need to be provisioned in secret storage
- Dependencies on external infrastructure (Elasticsearch, Kafka, MinIO/S3, etc.)
- Load balancer requirements - some modules don't use HTTP and require a load balancer which can work w/ arbitrary TCP traffic
- Non-standard health check endpoints
Assumptions
N/A
Constraints
N/A
Rationale
N/A
Decision
Teams must document deployment requirements in a clear & consistent way
Implications
- Pros
- N/A
- Cons
- N/A
Other Related Resources