Issue with CI/CD Pipeline Due to go.mod Replace Directive

Description:

I've noticed an issue within our CI/CD pipeline regarding the handling of the go.mod file in our microservice project. Specifically, the use of the replace directive and local version declaration for github.com/octoposprime/op-be-shared seems to be causing complications.

Problem:

When we include the following lines in our go.mod file:

replace github.com/octoposprime/op-be-shared => ../op-be-shared
github.com/octoposprime/op-be-shared v0.0.0-00010101000000-000000000000

The CI/CD pipeline is affected, as it's not correctly resolving dependencies during the build process.

Expected Behavior:

Ideally, our CI/CD pipeline should seamlessly handle the dependencies, including any replacements and local versions declared in the go.mod file, ensuring consistent and reliable builds across environments.

Current Workaround:

Currently, we're able to circumvent this issue by removing the replace directive and the local version declaration from the go.mod file. However, this isn't an optimal solution as it might lead to inconsistencies in dependency versions.

Proposed Solution:

We need to investigate and implement a solution that allows us to maintain the replace directive and the local version declaration for github.com/octoposprime/op-be-shared in our go.mod file while ensuring our CI/CD pipeline can successfully resolve dependencies during the build process.

Any insights or suggestions on how to address this issue would be greatly appreciated.

octoposprime / op-be-user