-
Story
-
Resolution: Done
-
Normal
-
s2i-1.4
Story (Required)
Update s2i to use golang 1.22. This ensures we are on the latest supported golang version from RHEL.
<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>
Background (Required)
<Describes the context or background related to this story>
Regular update of s2i's dependencies.
Out of scope
<Defines what is not included in this story>
- Dependency updates not tied to the golang update.
- Provide UBI9 image.
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
- Update go version in `go.mod` to 1.22
- Update Dockerfile to use UBI8 go-toolset for 1.22 - this might already be done if we are using Konflux to bump base images in Containerfiles.
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Go toolset for 1.22
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
- s2i container image uses golang 1.22
- Tests/checks pass.
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met