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
Is your feature request related to a problem? Please describe.
Currently, OCB provides method for replacement of collector components using the path value and generic module replacements using the replaces yaml value.
However, if a local module replaces/imports other modules that are not available from source/GOPROXY, ocb fails to compile if each direct and implicit dependency is not specified under replaces. This can be time-consuming and would have to be done manually every time a dependency is updated that meets this condition.
Describe the solution you'd like
It would be great if ocb could respect local module's local replacements (if I import module X locally, and X has replacements for modules Y and Z, ocb should check first if the directories exist for Y and Z before trying to download from source/proxy.
Describe alternatives you've considered
Go mod does not support this natively so I am not sure there is an alternative method; the alternative is just not supporting this functionality
Alternatively we could add a flag to enable/disable this behavior if this causes unexpected outcomes for those using ocb in production, something like --recursive-local-replacements
The text was updated successfully, but these errors were encountered:
this would be mainly useful for integration testing, building modules with ocb in pipelines with source code that has changed but not yet been published.
Is your feature request related to a problem? Please describe.
Currently, OCB provides method for replacement of collector components using the
path
value and generic module replacements using thereplaces
yaml value.However, if a local module replaces/imports other modules that are not available from source/GOPROXY, ocb fails to compile if each direct and implicit dependency is not specified under
replaces
. This can be time-consuming and would have to be done manually every time a dependency is updated that meets this condition.Describe the solution you'd like
It would be great if ocb could respect local module's local replacements (if I import module X locally, and X has replacements for modules Y and Z, ocb should check first if the directories exist for Y and Z before trying to download from source/proxy.
Describe alternatives you've considered
Go mod does not support this natively so I am not sure there is an alternative method; the alternative is just not supporting this functionality
Alternatively we could add a flag to enable/disable this behavior if this causes unexpected outcomes for those using ocb in production, something like
--recursive-local-replacements
The text was updated successfully, but these errors were encountered: