Kostas Chalikias07/06/2020, 1:22 PM
nicholas07/06/2020, 2:08 PM
you use to build the Flow. With that, your agent won't need to have access to those dependencies, just the registry you use to store the Docker image. GCS, however, stores your Flow as bytes in your bucket of choice but does not serialize your dependencies; in this case, your agent would need to have access whether through virtual env or otherwise) to the dependencies you mention in your Flow. 2. I'll let the community chime in here but generally any flows that don't use file-based storage will need to be re-registered when any changes are made. Doing so will re-serialize the Flow and bump the version number. Some users have more complicated CI/CD pipelines that might be helpful, particularly if you have some specific questions
Kostas Chalikias07/06/2020, 2:16 PM
nicholas07/06/2020, 3:15 PM
tab of the Flow page.
Kostas Chalikias07/06/2020, 3:24 PM
nicholas07/06/2020, 3:38 PM
or later, you won't need to re-register the flow if the metadata of the flow hasn't changed, so code changes within tasks don't require re-registration. This is not the case with prior versions.