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
It looks as though a recent change has impacted the way that the task image inherits environment variables.
With uselagoon/database-image-task:v0.0.1: the task was able to dump the database and push the image to the registry
With uselagoon/database-image-task:v0.0.3 (latest): mtk failed to dump the database. I think because of this change v0.0.1...v0.0.3, calc_MTK_variable() was not able to set up the MTK_DUMP_ variables based on the Lagoon variables.
Although the image is supposed to read the BUILDER_ variables from Lagoon project variables, it failed to do so with v0.0.3
it looks as though only environment variables can be read.
The text was updated successfully, but these errors were encountered:
Although the image is supposed to read the BUILDER_ variables from Lagoon project variables, it failed to do so with v0.0.3
it looks as though only environment variables can be read.
I think reading from the project variables is maybe a bug in the remote or core in how the project scoped variables are sent to the remote, and not an issue with this image.
It looks like the project scope variables are not being passed to the task correctly.
The issue with the project scoped variables missing from tasks will be resolved by uselagoon/lagoon#3856 as it changes the way that variables are sent to builds and tasks
It looks as though a recent change has impacted the way that the task image inherits environment variables.
Although the image is supposed to read the BUILDER_ variables from Lagoon project variables, it failed to do so with v0.0.3
it looks as though only environment variables can be read.
The text was updated successfully, but these errors were encountered: