Move plugin registry under the pkg/app/pipedv1/plugin (#5470)

Signed-off-by: Yoshiki Fujikane <ffjlabo@gmail.com>
pipe-cd · Jan 8, 2025 · fdd31ae · fdd31ae
1 parent 48be6ed
commit fdd31ae
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 12 deletions.
diff --git a/pkg/plugin/registry/registry.go → pkg/app/pipedv1/plugin/registry.go b/pkg/plugin/registry/registry.go → pkg/app/pipedv1/plugin/registry.go
@@ -12,12 +12,7 @@
 // See the License for the specific language governing permissions and
 // limitations under the License.
 
-// Package planner provides a piped component
-// that decides the deployment pipeline of a deployment.
-// The planner bases on the changes from git commits
-// then builds the deployment manifests to know the behavior of the deployment.
-// From that behavior the planner can decides which pipeline should be applied.
-package registry
+package plugin
 
 import (
 	"context"

diff --git a/pkg/plugin/registry/registry_test.go → pkg/app/pipedv1/plugin/registry_test.go b/pkg/plugin/registry/registry_test.go → pkg/app/pipedv1/plugin/registry_test.go
@@ -12,12 +12,7 @@
 // See the License for the specific language governing permissions and
 // limitations under the License.
 
-// Package planner provides a piped component
-// that decides the deployment pipeline of a deployment.
-// The planner bases on the changes from git commits
-// then builds the deployment manifests to know the behavior of the deployment.
-// From that behavior the planner can decides which pipeline should be applied.
-package registry
+package plugin
 
 import (
 	"testing"