Merge pull request #425 from robnester-rh/EC-1113

chore: update references to policy repo

Author: robnester-rh

README.md

@@ -32,7 +32,7 @@ there are several extensions defined as development dependencies in
 To make changes locally to the extensions run `npm run dev:setup` script in the
 `antora` directory. The script assumes that the local clones of
 [ec-cli](https://github.com/enterprise-contract/ec-cli/) and
-[ec-policies](https://github.com/enterprise-contract/ec-policies/) repositories
+[policy](https://github.com/conforma/policy/) repositories
 are present in the directory above this one. The outcome of running the
 `dev:setup` script is that local copies of the NPM packages that comprise the
 extensions are [linked](https://docs.npmjs.com/cli/v6/commands/npm-link), so

antora/README.md

@@ -18,7 +18,7 @@ With `hack/local-build.sh` script performs this by creating a temporary playbook
 file pointing to the local clones of the mentioned repositories if those
 repositories are located in the `../<repository>` for a
 `https://github.com/<org>/<repository>.git` git URL. For example, it is expected
-that the `ec-policies` repository is located at `../ec-policies`. If the local
+that the `policy` repository is located at `../policy`. If the local
 repository is on a different path create a symlink pointing from
 `../<repository>` to that path.
 

antora/antora-playbook.yml

@@ -26,7 +26,7 @@ site:
   robots: allow
 content:
   sources:
-    - url: https://github.com/enterprise-contract/ec-policies.git
+    - url: https://github.com/conforma/policy.git
       start_path: antora/docs
 
     - url: https://github.com/enterprise-contract/ec-cli.git

antora/supplemental-ui/helpers/componentTitle.cjs

@@ -6,7 +6,7 @@ const customTitles = {
   "user-guide": "About",
   "ec-cli": "CLI Reference",
   "ecc": "Configuration Reference",
-  "ec-policies": "Policies",
+  "policy": "Policies",
 }
 
 module.exports = (component) => {

antora/supplemental-ui/helpers/sortComponents.cjs

@@ -8,7 +8,7 @@ const componentOrder = [
   "user-guide",
   "ec-cli",
   "ecc",
-  "ec-policies",
+  "policy",
 ]
 
 const componentSorter = function (a, b) {

conforma.github.io.code-workspace

@@ -13,7 +13,7 @@
 			"path": "../ec-cli/tekton-task-antora-extension"
 		},
 		{
-			"path": "../ec-policies/antora/ec-policies-antora-extension"
+			"path": "../policy/antora/policy-antora-extension"
 		}
 	],
 	"settings": {}

website/config/_default/menu.toml

@@ -44,7 +44,7 @@
   [[main]]
     name = 'Policies'
     parent = 'Documentation'
-    url = '/docs/ec-policies/release_policy.html'
+    url = '/docs/policy/release_policy.html'
     weight = 60
 
   [[main]]

website/content/posts/a-taste-of-policies.md

@@ -67,8 +67,8 @@ identity:
 
 sources:
   - policy:
-      - github.com/enterprise-contract/ec-policies//policy/lib
-      - github.com/enterprise-contract/ec-policies//policy/release
+      - github.com/conforma/policy//policy/lib
+      - github.com/conforma/policy//policy/release
     ruleData:
       allowed_gh_workflow_repos:
         - lcarva/festoji
@@ -86,7 +86,7 @@ configuration:
 
 This policy moves the certificate flags to the policy itself. It also specifies certain policy rules
 to be executed. Here we are including some of the existing Enterprise Contract policy rules,
-[github_certificate](https://conforma.dev/docs/ec-policies/release_policy.html#github_certificate_package).
+[github_certificate](https://conforma.dev/docs/policy/release_policy.html#github_certificate_package).
 These policy rules rely on certain data to be provided, e.g. the expected GitHub Workflow
 repository. With this policy saved as `policy.yaml`, we can simplify how the CLI is invoked:
 
@@ -189,7 +189,7 @@ deny contains result if {
 This defines a single policy rule that verifies the materials section of the SLSA Provenance contain
 the expected git repository. The Enterprise Contract relies on rego annotations to provide
 additional information about each of the policy rules. See the
-[docs](https://conforma.dev/docs/ec-policies/authoring.html) for more information.
+[docs](https://conforma.dev/docs/policy/authoring.html) for more information.
 
 Let's add this rule to our previous policy:
 
@@ -202,8 +202,8 @@ identity:
 
 sources:
   - policy:
-      - github.com/enterprise-contract/ec-policies//policy/lib
-      - github.com/enterprise-contract/ec-policies//policy/release
+      - github.com/conforma/policy//policy/lib
+      - github.com/conforma/policy//policy/release
     ruleData:
       allowed_gh_workflow_repos:
         - lcarva/festoji

website/content/posts/evaluating-custom-predicates.md

@@ -111,7 +111,7 @@ _bacon_attestations := [attestation |
 ]
 ```
 
-(Check out the [docs](https://conforma.dev/docs/ec-policies/authoring.html) for more
+(Check out the [docs](https://conforma.dev/docs/policy/authoring.html) for more
 information on how to author policy rules 🔥)
 
 Next, we create a policy configuration, `policy.yaml`, to use the policy rules above.

website/content/posts/gating-image-promotion-on-gitlab.md

@@ -250,8 +250,8 @@ identity:
   issuer: https://gitlab.com
 sources:  # <- added
   - policy:
-      - github.com/enterprise-contract/ec-policies//policy/lib
-      - github.com/enterprise-contract/ec-policies//policy/release
+      - github.com/conforma/policy//policy/lib
+      - github.com/conforma/policy//policy/release
     config:
       include:
         - slsa_source_correlated
@@ -296,7 +296,7 @@ GitLab.
 [GitLab container registry]: https://docs.gitlab.com/ee/user/packages/container_registry/
 [identity-based]: https://docs.sigstore.dev/signing/overview/
 [SLSA Provenance]: https://slsa.dev/spec/v1.0/
-[slsa_source_correlated]: https://conforma.dev/docs/ec-policies/release_policy.html#slsa_source_correlated_package
+[slsa_source_correlated]: https://conforma.dev/docs/policy/release_policy.html#slsa_source_correlated_package
 
 ## Appendix