manifest-generate-paths annotation is used in webhook to eliminate unnecessary trigger of application reconciliation. The logic behind manifest-generate-paths is to list down files that related to the application, and ignore unused files in repository.
The manifest-generate-paths, however, does not help in sidecar config management plugin. In sidecar case, the git repository, excluding reposerver.plugin.tar.exclusions, is compressed and sent to sidecar to generate application resources, even when some of the contents in git repository are not needed.
Motivation
When using monorepo, there are lots of applications depends on single git repository, and each application only use small subset of files. With manifest-generate-paths, only files needed by application are sent to sidecar to reduce unnecessary compression/decompression.
Proposal
Add a configuration to enable filter out unnecessary in sidecar config management plugin.
When the configuration is on, only files in manifest-generate-paths are sent to sidecar config management plugin to generate application.
Summary
manifest-generate-paths
annotation is used in webhook to eliminate unnecessary trigger of application reconciliation. The logic behindmanifest-generate-paths
is to list down files that related to the application, and ignore unused files in repository.The
manifest-generate-paths
, however, does not help in sidecar config management plugin. In sidecar case, the git repository, excludingreposerver.plugin.tar.exclusions
, is compressed and sent to sidecar to generate application resources, even when some of the contents in git repository are not needed.Motivation
When using monorepo, there are lots of applications depends on single git repository, and each application only use small subset of files. With
manifest-generate-paths
, only files needed by application are sent to sidecar to reduce unnecessary compression/decompression.Proposal
manifest-generate-paths
are sent to sidecar config management plugin to generate application.