replicatedhq / replicatedhq/platform-examples
feat(mlflow): add license field wiring pattern (KOTS Config to app ConfigMap)
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Parent epic: #166
Integration branch: feat/mlflow-enterprise-patterns
Wire KOTS license entitlements through Config → HelmChart CR values → application ConfigMap so the app can consume license fields like tier and max_users.
Scope
- Add Config items to
release/kots-config.yamlusing{{repl LicenseFieldValue "tier"}}and{{repl LicenseFieldValue "max_users"}} - Map Config items into HelmChart CR values in
release/mlflow-chart.yamlasvalues.license.* - Create
charts/mlflow/templates/license-configmap.yamlthat reads.Values.license.*and creates a ConfigMap for app consumption - Add
licensesection tocharts/mlflow/values.yamlwith defaults
Files touched
applications/mlflow/release/kots-config.yaml(add license Config items)applications/mlflow/release/mlflow-chart.yaml(add license values mapping)applications/mlflow/charts/mlflow/templates/license-configmap.yaml(new file)applications/mlflow/charts/mlflow/values.yaml(add license section)
PR target
Branch PRs to feat/mlflow-enterprise-patterns (not main).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing patterns in applications/mlflow/release/kots-config.yaml and applications/mlflow/release/mlflow-chart.yaml, then inspect charts/mlflow/values.yaml and its templates. Add the tier and max_users flow across the four named files, and verify that the resulting application ConfigMap exposes those license fields when deployed through the integration branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100