Nephio is a Kubernetes-based automation platform for deploying and managing highly distributed, interconnected workloads such as 5G Network Functions, and the underlying infrastructure on which those workloads depend.
When an upstream repository of repositories.config.porch.kpt.dev is updated then it is not taken into account until we delete the repositories.config.porch.kpt.dev object and re-create it.
For example, there is a package in GitHub-repo-a and I register that repository via
Then deploy package GitHub-repo-a and then delete it, update the upstream repository GitHub-repo-a and create it again. It won't consider the latest commit, it will take the commit when the repository was registered.
Now the question is, is this a bug or that is how it is designed?
When an upstream repository of
repositories.config.porch.kpt.dev
is updated then it is not taken into account until we delete therepositories.config.porch.kpt.dev
object and re-create it.For example, there is a package in
GitHub-repo-a
and I register that repository viaThen deploy package
GitHub-repo-a
and then delete it, update the upstream repositoryGitHub-repo-a
and create it again. It won't consider the latest commit, it will take the commit when the repository was registered.Now the question is, is this a bug or that is how it is designed?