Updated docs to remove mention of mutators/validators against Repository from Porch Orchestration page (#205)

The corresponding change in Repository API spec is covered in following
Porch PR
nephio-project/porch#179

Author: gkumar78

content/en/docs/porch/contributors-guide/_index.md

@@ -27,8 +27,8 @@ Porch comprises of several software components:
   operations on package contents
 * [func](https://github.com/nephio-project/porch/tree/main/func): KRM function evaluator microservice; exposes gRPC API
 * [repository](https://github.com/nephio-project/porch/blob/main/pkg/repository): Repository integration package
-* [git](https://github.com/nephio-project/porch/tree/main/pkg/git): Integration with Git repository.
-* [oci](https://github.com/nephio-project/porch/tree/main/pkg/oci): Integration with OCI repository.
+* [git](https://github.com/nephio-project/porch/tree/main/pkg/externalrepo/git): Integration with Git repository.
+* [oci](https://github.com/nephio-project/porch/tree/main/pkg/externalrepo/oci): Integration with OCI repository.
 * [cache](https://github.com/nephio-project/porch/tree/main/pkg/cache): Package caching.
 * [controllers](https://github.com/nephio-project/porch/tree/main/controllers): `Repository` CRD. No controller;
   Porch apiserver watches these resources for changes as repositories are (un-)registered.
@@ -81,8 +81,8 @@ Some useful code pointers:
 * Porch REST API handlers in [registry/porch](https://github.com/nephio-project/porch/tree/main/pkg/registry/porch),
   for example [packagerevision.go](https://github.com/nephio-project/porch/tree/main/pkg/registry/porch/packagerevision.go)
 * Background task handling cache updates in [background.go](https://github.com/nephio-project/porch/tree/main/pkg/registry/porch/background.go)
-* Git repository integration in [pkg/git](https://github.com/nephio-project/porch/tree/main/pkg/git)
-* OCI repository integration in [pkg/oci](https://github.com/nephio-project/porch/tree/main/pkg/oci)
+* Git repository integration in [pkg/git](https://github.com/nephio-project/porch/tree/main/pkg/externalrepo/git)
+* OCI repository integration in [pkg/oci](https://github.com/nephio-project/porch/tree/main/pkg/externalrepo/oci)
 * CaD Engine in [engine](https://github.com/nephio-project/porch/tree/main/pkg/engine)
 * e2e tests in [e2e](https://github.com/nephio-project/porch/tree/main/test/e2e). See below more on testing.
 
@@ -113,4 +113,4 @@ then run test suite against the Porch instance.
 
 [VS Code](https://code.visualstudio.com/) works really well for editing and debugging.
 Just open VSCode from the root folder of the Porch repository and it will work fine. The folder contains the needed
-configuration to Launch different functions of Porch.
+configuration to Launch different functions of Porch.

content/en/docs/porch/package-orchestration.md

@@ -98,9 +98,6 @@ associated with package to capture:
 At repository registration, customers must be able to specify details needed to store packages in appropriate locations
 in the repository. For example, registration of a Git repository must accept a branch and a directory.
 
-Repositories may have associated guardrails - mutation and validation functions that ensure and enforce requirements of
-all packages in the repository, including gating promotion of a package to a *published* lifecycle stage.
-
 {{% alert title="Note" color="primary" %}}
 
 A user role with sufficient permissions can register a package or function repository, including repositories
@@ -170,9 +167,6 @@ The repository management functionality of Package Orchestration service enables
   packages will be cloned.
 * annotate repository with metadata such as whether repository contains deployment ready packages or not; metadata can
   be application or customer specific
-* define and enforce package invariants (guardrails) at the repository level, by registering mutator and/or validator
-  functions with the repository; those registered functions will be applied to packages in the repository to enforce
-  invariants
 
 ### Package Discovery
 
@@ -217,10 +211,8 @@ The package authoring and lifecycle functionality of the package Orchestration s
 
 * Rebase a package onto another upstream base package or onto a newer version of the same package (to
   aid with conflict resolution during the process of publishing a draft package)
-* Get feedback during package authoring, and assistance in recovery from:
 
-  * merge conflicts, invalid package changes, guardrail violations
-  * compliance of the drafted package with repository-wide invariants and guardrails
+* Get feedback during package authoring, and assistance in recovery from merge conflicts, invalid package changes, guardrail violations
 
 * Propose for a _draft_ package be _published_.
 * Apply an arbitrary decision criteria, and by a manual or automated action, approve (or reject) proposal of a _draft_
@@ -229,7 +221,7 @@ The package authoring and lifecycle functionality of the package Orchestration s
 
   * Assisted/automated update (upgrade, rollback) of groups of packages matching specific criteria (i.e. base package
     has new version or specific base package version has a vulnerability and should be rolled back)
-  * Proposed change validation (pre-validating change that adds a validator function to a base package or a repository)
+  * Proposed change validation (pre-validating change that adds a validator function to a base package)
 
 * Delete an existing package.
 
@@ -402,4 +394,4 @@ Kubernetes apiserver are:
 [apiserver]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
 [representation]: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#differing-representations
 [crds]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
-[oci]: https://github.com/opencontainers/image-spec/blob/main/spec.md
+[oci]: https://github.com/opencontainers/image-spec/blob/main/spec.md