docs: update docs to reference name instead of id (#1059)

Signed-off-by: Miguel Martinez Trivino <[email protected]>

Author: migmartri

docs/docs/getting-started/workflow-definition.mdx

@@ -55,11 +55,11 @@ $ chainloop workflow create \
 By default, if no contract is provided, a new, empty one will be created
 
 ```bash
-$ chainloop workflow contract describe --id fd489047-67f1-45d4-9f3b-27eba4051929
+$ chainloop workflow contract describe --name build-and-test
 ┌─────────────────────────────────────────────────────────────┐
 │ Contract                                                    │
 ├──────────────────────┬──────────────────────────────────────┤
-│ Name                 │ build-and-test generated schema      │
+│ Name                 │ build-and-test                       │
 ├──────────────────────┼──────────────────────────────────────┤
 │ ID                   │ fd489047-67f1-45d4-9f3b-27eba4051929 │
 ├──────────────────────┼──────────────────────────────────────┤
@@ -114,8 +114,7 @@ Update the name and schema, notice the revision increment
 
 ```bash
 $ chainloop workflow contract update \
-   --id fd489047-67f1-45d4-9f3b-27eba4051929 \
-   --name skynet-contract \
+   --name build-and-test \
    -f https://raw.githubusercontent.com/chainloop-dev/chainloop/main/docs/examples/contracts/skynet/contract.yaml
 
 ┌─────────────────────────────────────────────────────────────┐

docs/docs/guides/dependency-track/dependency-track.mdx

@@ -58,7 +58,7 @@ Using the [Chainloop CLI](/getting-started/installation), you can register an in
 This is done via the `chainloop integration registered add` command but first let's find out what are the required inputs using the `available describe` command.
 
 ```bash
-$ chainloop integration available describe --id dependency-track
+$ chainloop integration available describe --name dependency-track
 
 ┌──────────────────┬─────────┬──────────────────────┬────────────────────────────────────────────────────────┐
 │ ID               │ VERSION │ MATERIAL REQUIREMENT │ DESCRIPTION                                            │
@@ -104,7 +104,7 @@ The attachment is done via `chainloop integration attached add` command. But as
 
 
 ```bash
-$ chainloop integration available describe --id dependency-track
+$ chainloop integration available describe --name dependency-track
 
 ┌──────────────────┬─────────┬──────────────────────┬────────────────────────────────────────────────────────┐
 │ ID               │ VERSION │ MATERIAL REQUIREMENT │ DESCRIPTION                                            │

docs/docs/guides/guac/guac.mdx

@@ -63,7 +63,7 @@ Currently, this integration only supports [Google Cloud Storage](https://cloud.g
 To get started, you need to register the integration in your Chainloop organization. To know what parameters are accepted, you can use the `chainloop integration available describe` command.
 
 ```bash
-$ chainloop integration available describe --id guac                              
+$ chainloop integration available describe --name guac                              
 ┌──────┬─────────┬─────────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────┐
 │ ID   │ VERSION │ MATERIAL REQUIREMENT                │ DESCRIPTION                                                                                    │
 ├──────┼─────────┼─────────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤

docs/docs/guides/sbom-management/sbom-management.mdx

@@ -51,7 +51,7 @@ export CONTRACT_ID=<your_contract_id>
 
 Please check your contract to confirm that it is currently empty.
 ```
-chainloop wf contract describe --id $CONTRACT_ID
+chainloop wf contract describe --name $CONTRACT_ID
 [...]
 {
   "schemaVersion": "v1"
@@ -66,7 +66,6 @@ We will add one requirement to our contract to ensure Developers provide a Cyclo
 
 ```bash
 chainloop workflow contract update \
- --id $CONTRACT_ID \
  --name my-contract \
  -f https://github.com/chainloop-dev/chainloop/blob/main/docs/examples/contracts/sbom/cyclonedx.yaml
 ```

docs/docs/integrations/development/overview.md

@@ -62,7 +62,7 @@ $ chainloop integration available list
 And the information of how to use it can be found in the describe command.
 
 ```console
-$ chainloop integration available describe --id dependencytrack
+$ chainloop integration available describe --name dependencytrack
 ┌─────────────────┬─────────┬──────────────────────┬────────────────────────────────────────────────────────┐
 │ ID              │ VERSION │ MATERIAL REQUIREMENT │ DESCRIPTION                                            │
 ├─────────────────┼─────────┼──────────────────────┼────────────────────────────────────────────────────────┤

docs/docs/integrations/integrations.md

@@ -51,7 +51,7 @@ Registration is when a specific instance of the integration is configured on a C
 In our case, we want to register an instance of the `oci-registry` integration. To do so, we need to first figure out what configuration parameters are required by the integration. We can do so by running:
 
 ```sh
-$ chainloop integration available describe --id oci-registry
+$ chainloop integration available describe --name oci-registry
 ┌──────────────┬─────────┬──────────────────────┬────────────────────────────────────────────────┐
 │ ID           │ VERSION │ MATERIAL REQUIREMENT │ DESCRIPTION                                    │
 ├──────────────┼─────────┼──────────────────────┼────────────────────────────────────────────────┤

docs/docs/quickstart.md

@@ -87,7 +87,7 @@ This quickstart will guide you through the process of installing the Chainloop C
     For example, to list the workflows you can run: 
 
     ```bash
-    # List workflow runs, so then you can do `workflow run describe --id <id>` to get more details
+    # List workflow runs, so then you can do `workflow run describe --name <workflow-name>` to get more details
     chainloop workflow run ls
     ```