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
When publishing plans, each tasks _init_options ends up getting run twice.
The metadeploy_publish task appears to be running _init_options before upload and then saving the modified options as the options for each step on the new upload. Then, when a user runs a plan through Metadeploy, _init_options runs again, this time starting with the already modified options.
This becomes a big problem if _init_options ever modifies the option values provided in the original flow. This is currently breaking the retrieve_unpackaged task because it is overwriting the package_xml option which is supposed to have a file path, with the file content. This means Metadeploy attempts to retrieve a file from a completely non-sensical file path.
The text was updated successfully, but these errors were encountered:
When publishing plans, each tasks _init_options ends up getting run twice.
The metadeploy_publish task appears to be running _init_options before upload and then saving the modified options as the options for each step on the new upload. Then, when a user runs a plan through Metadeploy, _init_options runs again, this time starting with the already modified options.
This becomes a big problem if _init_options ever modifies the option values provided in the original flow. This is currently breaking the retrieve_unpackaged task because it is overwriting the package_xml option which is supposed to have a file path, with the file content. This means Metadeploy attempts to retrieve a file from a completely non-sensical file path.
The text was updated successfully, but these errors were encountered: