-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
False
-
-
-
-
1. Proposed title of this feature request
-> Dynamic Versioning of ImageStreams
2. What is the nature and description of the request?
-> Project is building Container Image based on an external Resource (Java Jar) inside of OCP. Resources are prebuilt outside of OCP and are tagged in a Repository. (Outside of OCP as well). OCP BuildConfig is triggered by Webhook with ENV Params via HTTP.
ENVs are passed through BuildConfig to Dockerfile. These Params could be used to tag the Output of the BuildConfig. (e.g. my.package.application:${ENV_PARAM_VERSION} )
3. Why does the customer need this? (List the business requirements here)
-> Separation of Buildartifacts (created inside/outside of OCP)
-> Reuse versioning logic from previous build steps
4. How would the customer like to achieve this? (List the functional requirements here)
-> OPTIONAL -> max. archived tags -> delete older as
-> Useage of Webhook Env Params in BuildConfig.
output:
to:
kind: ImageStreamTag
name: my-app:${env.VERSION_PARAM}
5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
-> list versions and deletes artifacts older as / amount greater as
-> parsing check during yaml apply