You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Have the datafy CLI print a warning if the used spark images are not the latest “service release”.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We recently had an outage because someone of the team rebuild the solution with an older image version. This version contained an incompatibility between debian and setuptools that was fixed in the latest release of the the datafy images. The user was not aware of the issue causing us to troubleshoot the issue over the weekend.
Are you currently working around this issue?
We update the image but no structural plan in place to solve this issue
Additional context
Submitted on behalf of Lieven.
Attachments
The text was updated successfully, but these errors were encountered:
pascal-knapen
changed the title
[request]: describe request here
[request]: Print warning message in the CLI when new datafy images are available
Jan 31, 2022
Community Note
Tell us about your request
Have the datafy CLI print a warning if the used spark images are not the latest “service release”.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We recently had an outage because someone of the team rebuild the solution with an older image version. This version contained an incompatibility between debian and setuptools that was fixed in the latest release of the the datafy images. The user was not aware of the issue causing us to troubleshoot the issue over the weekend.
Are you currently working around this issue?
We update the image but no structural plan in place to solve this issue
Additional context
Submitted on behalf of Lieven.
Attachments
The text was updated successfully, but these errors were encountered: