Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate datajobs.vdk.image AND datajobs.deployment.dataJobBaseImage Properties #1929

Closed
doks5 opened this issue Apr 19, 2023 · 0 comments · Fixed by #2075
Closed

Deprecate datajobs.vdk.image AND datajobs.deployment.dataJobBaseImage Properties #1929

doks5 opened this issue Apr 19, 2023 · 0 comments · Fixed by #2075
Assignees
Labels

Comments

@doks5
Copy link
Contributor

doks5 commented Apr 19, 2023

What is the feature request? What problem does it solve?
With the introduction of support for multiple python versions, the datajobs.vdk.image and datajobs.deployment.dataJobBaseImage application properties would no longer be used, and are to be replaced by the datajobs.deployment.supportedPythonVersions and datajobs.deployment.defaultPythonVersion configurations.

Suggested solution
After the implementation of the new logic and configuration to support multiple python versions is complete, remove the datajobs.vdk.image and datajobs.deployment.dataJobBaseImage properties from the properties scripts, the helm chart and the TODOs mentioned in the source code of the Control Service.

Additional context
TBC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant