orange-cloudfoundry/cf-ops-automation

View on GitHub
docs/features/features.html

Summary

Maintainability
Test Coverage

TODO found
Open

{"gherkinDocument":{"uri":"features/cf_app_deployment_environment_variable_available.feature","feature":{"location":{"line":1,"column":1},"tags":[],"language":"en","keyword":"Feature","name":"Cf application deployment support","description":"  In order to know how to deploy a CF application\n  As a paas-template user,\n  I want to know which environment varaiables are availlable","children":[{"background":{"location":{"line":6,"column":3},"keyword":"Background","name":"","description":"","steps":[{"location":{"line":7,"column":5},"keyword":"Given ","text":"Hello world generated pipelines from reference_dataset","id":"b7ea8156-b790-4b68-a2b5-7e771c16f896"}],"id":"34e373a8-9e28-4f11-a3e9-9ccdc77d52b5"}},{"scenario":{"location":{"line":9,"column":3},"tags":[],"keyword":"Scenario","name":"a deployment, or a part, is done using a concourse pipeline","description":"","steps":[{"location":{"line":10,"column":5},"keyword":"But ","text":"needs documentation","id":"7966ef57-5747-4c39-9419-82e2ed4aa157"}],"examples":[],"id":"f33ee53b-6f32-4db3-972e-82e4d2d4581e"}}]},"comments":[{"location":{"line":11,"column":1},"text":"#    Then the following environment variables exist:"},{"location":{"line":12,"column":1},"text":"#      | name              | description                                                                     |"},{"location":{"line":13,"column":1},"text":"#      | GENERATE_DIR      | directory holding generated files. It's an absolute path.                       |"},{"location":{"line":14,"column":1},"text":"#      | BASE_TEMPLATE_DIR | directory where `pre-cf-push.sh` is located. It's an relative path.             |"},{"location":{"line":15,"column":1},"text":"#      | SECRETS_DIR       | directory holding secrets related to current deployment. It's an relative path. |"},{"location":{"line":16,"column":1},"text":"#      | CF_API_URL        | current application Cloud Foundry API url                                       |"},{"location":{"line":17,"column":1},"text":"#      | CF_USERNAME       | current Cloud Foundry application user                                          |"},{"location":{"line":18,"column":1},"text":"#      | CF_PASSWORD       | current Cloud Foundry application user password                                 |"},{"location":{"line":19,"column":1},"text":"#      | CF_ORG            | current Cloud Foundry application organization                                  |"},{"location":{"line":20,"column":1},"text":"#      | CF_SPACE          | current Cloud Foundry application space                                         |"},{"location":{"line":21,"column":1},"text":"#      | CUSTOM_SCRIPT_DIR | TODO                                         |"},{"location":{"line":22,"column":1},"text":"#      | CF_MANIFEST       | TODO                                         |"},{"location":{"line":23,"column":1},"text":"#"}]}},
Severity: Minor
Found in docs/features/features.html by fixme

TODO found
Open

{"source":{"uri":"features/cf_app_deployment_environment_variable_available.feature","data":"Feature: Cf application deployment support\n  In order to know how to deploy a CF application\n  As a paas-template user,\n  I want to know which environment varaiables are availlable\n\n  Background:\n    Given Hello world generated pipelines from reference_dataset\n\n  Scenario: a deployment, or a part, is done using a concourse pipeline\n    But needs documentation\n#    Then the following environment variables exist:\n#      | name              | description                                                                     |\n#      | GENERATE_DIR      | directory holding generated files. It's an absolute path.                       |\n#      | BASE_TEMPLATE_DIR | directory where `pre-cf-push.sh` is located. It's an relative path.             |\n#      | SECRETS_DIR       | directory holding secrets related to current deployment. It's an relative path. |\n#      | CF_API_URL        | current application Cloud Foundry API url                                       |\n#      | CF_USERNAME       | current Cloud Foundry application user                                          |\n#      | CF_PASSWORD       | current Cloud Foundry application user password                                 |\n#      | CF_ORG            | current Cloud Foundry application organization                                  |\n#      | CF_SPACE          | current Cloud Foundry application space                                         |\n#      | CUSTOM_SCRIPT_DIR | TODO                                         |\n#      | CF_MANIFEST       | TODO                                         |\n#\n","mediaType":"text/x.cucumber.gherkin+plain"}},
Severity: Minor
Found in docs/features/features.html by fixme

TODO found
Open

{"source":{"uri":"features/cf_app_deployment_environment_variable_available.feature","data":"Feature: Cf application deployment support\n  In order to know how to deploy a CF application\n  As a paas-template user,\n  I want to know which environment varaiables are availlable\n\n  Background:\n    Given Hello world generated pipelines from reference_dataset\n\n  Scenario: a deployment, or a part, is done using a concourse pipeline\n    But needs documentation\n#    Then the following environment variables exist:\n#      | name              | description                                                                     |\n#      | GENERATE_DIR      | directory holding generated files. It's an absolute path.                       |\n#      | BASE_TEMPLATE_DIR | directory where `pre-cf-push.sh` is located. It's an relative path.             |\n#      | SECRETS_DIR       | directory holding secrets related to current deployment. It's an relative path. |\n#      | CF_API_URL        | current application Cloud Foundry API url                                       |\n#      | CF_USERNAME       | current Cloud Foundry application user                                          |\n#      | CF_PASSWORD       | current Cloud Foundry application user password                                 |\n#      | CF_ORG            | current Cloud Foundry application organization                                  |\n#      | CF_SPACE          | current Cloud Foundry application space                                         |\n#      | CUSTOM_SCRIPT_DIR | TODO                                         |\n#      | CF_MANIFEST       | TODO                                         |\n#\n","mediaType":"text/x.cucumber.gherkin+plain"}},
Severity: Minor
Found in docs/features/features.html by fixme

TODO found
Open

{"gherkinDocument":{"uri":"features/cf_app_deployment_environment_variable_available.feature","feature":{"location":{"line":1,"column":1},"tags":[],"language":"en","keyword":"Feature","name":"Cf application deployment support","description":"  In order to know how to deploy a CF application\n  As a paas-template user,\n  I want to know which environment varaiables are availlable","children":[{"background":{"location":{"line":6,"column":3},"keyword":"Background","name":"","description":"","steps":[{"location":{"line":7,"column":5},"keyword":"Given ","text":"Hello world generated pipelines from reference_dataset","id":"b7ea8156-b790-4b68-a2b5-7e771c16f896"}],"id":"34e373a8-9e28-4f11-a3e9-9ccdc77d52b5"}},{"scenario":{"location":{"line":9,"column":3},"tags":[],"keyword":"Scenario","name":"a deployment, or a part, is done using a concourse pipeline","description":"","steps":[{"location":{"line":10,"column":5},"keyword":"But ","text":"needs documentation","id":"7966ef57-5747-4c39-9419-82e2ed4aa157"}],"examples":[],"id":"f33ee53b-6f32-4db3-972e-82e4d2d4581e"}}]},"comments":[{"location":{"line":11,"column":1},"text":"#    Then the following environment variables exist:"},{"location":{"line":12,"column":1},"text":"#      | name              | description                                                                     |"},{"location":{"line":13,"column":1},"text":"#      | GENERATE_DIR      | directory holding generated files. It's an absolute path.                       |"},{"location":{"line":14,"column":1},"text":"#      | BASE_TEMPLATE_DIR | directory where `pre-cf-push.sh` is located. It's an relative path.             |"},{"location":{"line":15,"column":1},"text":"#      | SECRETS_DIR       | directory holding secrets related to current deployment. It's an relative path. |"},{"location":{"line":16,"column":1},"text":"#      | CF_API_URL        | current application Cloud Foundry API url                                       |"},{"location":{"line":17,"column":1},"text":"#      | CF_USERNAME       | current Cloud Foundry application user                                          |"},{"location":{"line":18,"column":1},"text":"#      | CF_PASSWORD       | current Cloud Foundry application user password                                 |"},{"location":{"line":19,"column":1},"text":"#      | CF_ORG            | current Cloud Foundry application organization                                  |"},{"location":{"line":20,"column":1},"text":"#      | CF_SPACE          | current Cloud Foundry application space                                         |"},{"location":{"line":21,"column":1},"text":"#      | CUSTOM_SCRIPT_DIR | TODO                                         |"},{"location":{"line":22,"column":1},"text":"#      | CF_MANIFEST       | TODO                                         |"},{"location":{"line":23,"column":1},"text":"#"}]}},
Severity: Minor
Found in docs/features/features.html by fixme

There are no issues that match your filters.

Category
Status