4.6. Working with Life Cycle Environments

Procedure 4.3. Creating Linked Life Cycle Environments

1. Choose an existing Life Cycle Environment that you want to use as a starting point. List the environment using its ID, in this case the environment with ID 1:

   $ curl -X GET -s -k -u sat_user:sat_password \
   https://satellite6.example.com/katello/api/environments/1 | python -m json.tool
   	output omitted
      "id": 1,
      "label": "Library",
   	output omitted
       "prior": null,
       "successor": null,
   	output truncated

   Copy to Clipboard
2. Create a new Life Cycle Environment using the prior option set to 1:
   1. Create a JSON file, for example, life-cycle.json, with the following contents: {"organization_id":1,"label":"api-dev","name":"API Development","prior":1}
   2. Enter a command as follows:

      $ curl -H "Accept:application/json,version=2" \
      -H "Content-Type:application/json" -X POST \
      -u sat_user:sat_password -k \
      -d @life-cycle.json \
      https://satellite6.example.com/katello/api/environments \
      | python -m json.tool
            output omitted
          "description": null,
          "id": 2,
          "label": "api-dev",
          "library": false,
          "name": "API Development",
          "organization": {
              "id": 1,
              "label": "Default_Organization",
              "name": "Default Organization"
          },
          "permissions": {
              "destroy_lifecycle_environments": true,
              "edit_lifecycle_environments": true,
              "promote_or_remove_content_views_to_environments": true,
              "view_lifecycle_environments": true
          },
         "prior": {
              "id": 1,
              "name": "Library"
          },
      	output truncated

      Copy to Clipboard
   In the command output you can see the ID for this Life Cycle Environment is 2, and the Life Cycle Environment prior to this one is 1. This signifies that Life Cycle Environment 1 and 2 are linked. The Life Cycle Environment ID 2 is used when creating a successor to this environment.
3. Create another Life Cycle Environment, using the prior option set to 2:
   1. Edit the previously created life-cycle.json, updating the label, name, and prior values: {"organization_id":1,"label":"api-qa","name":"API QA","prior":2}
   2. Enter a command as follows:

      $ curl -H "Accept:application/json,version=2" \
      -H "Content-Type:application/json" -X POST \
      -u sat_user:sat_password -k \
      -d @life-cycle.json \
      https://satellite6.example.com/katello/api/environments \
      | python -m json.tool
            output omitted
         "description": null,
         "id": 3,
          "label": "api-qa",
          "library": false,
          "name": "API QA",
          "organization": {
              "id": 1,
              "label": "Default_Organization",
              "name": "Default Organization"
          },
          "permissions": {
              "destroy_lifecycle_environments": true,
              "edit_lifecycle_environments": true,
              "promote_or_remove_content_views_to_environments": true,
              "view_lifecycle_environments": true
          },
         "prior": {
              "id": 2,
              "name": "API Development"
          },
          "successor": null,
      	output truncated

      Copy to Clipboard
   In the command output you can see the ID for this Life Cycle Environment is 3, and the Life Cycle Environment prior to this one is 2. This signifies that Life Cycle Environment 2 and 3 are linked.