[ci skip] auto-update for release 2.2.0 - Changelog update

CHANGELOG.md

@@ -1,16 +1,47 @@
 # Change Log
 
-## [v2.1.0](https://github.com/orange-cloudfoundry/cf-ops-automation/tree/v2.1.0) (2018-06-20)
-[Full Changelog](https://github.com/orange-cloudfoundry/cf-ops-automation/compare/v1.9.1...v2.1.0)
+## [v2.2.0](https://github.com/orange-cloudfoundry/cf-ops-automation/tree/v2.2.0) (2018-07-26)
+[Full Changelog](https://github.com/orange-cloudfoundry/cf-ops-automation/compare/v2.1.0...v2.2.0)
 
 **Implemented enhancements:**
 
-- offer a preview in logs of interpolated \(manifest + operators + vars\) [\#52](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/52)
-- Add delete lifecycle [\#4](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/4)
+- Support online stemcell [\#128](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/128)
+- Support terraform provider UAA [\#120](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/120)
+- Terraform pipeline UX: single job to apply TF specs [\#22](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/22)
+
+**Fixed bugs:**
+
+- The job update-pipeline-\<root deployment\> is not triggered as expected [\#172](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/172)
 
 **Closed issues:**
 
+- Reset git to a previous commit [\#173](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/173)
+- terraform plan phase should not be recurrent daily, but triggered by secrets update [\#156](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/156)
+- add terraform azure support [\#153](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/153)
 - Regression: IAAS\_SPEC\_PATH is missing in Concourse pipelines  [\#151](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/151)
+- Remove consistency check on deployment-dependencies.yml\#deployment.\<dep\_name\> [\#150](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/150)
+- Setup a reference dataset [\#111](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/111)
+- Add living user documentation generated from tests [\#107](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/107)
+
+**Merged pull requests:**
+
+- task\(git\_reset\_wip\): create a commit after reset [\#174](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/174)
+- trigger update-pipeline on each`secrets-repo` commit and `init-concourse-boshrelease-and-stemcell` improvements [\#171](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/171)
+- Online stemcells support [\#169](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/169)
+- Terraform improvements [\#166](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/166)
+- allow usage of generic key in deployment-dependencies [\#163](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/163)
+- Living doc missing cf app hooks [\#161](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/161)
+- Upgrade script for config repo for upcoming release 2.2.0 [\#160](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/160)
+- pipeline\(depls\): collapse delete task to speed up concourse execution [\#154](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/154)
+- 107 living documentation refactored [\#149](https://github.com/orange-cloudfoundry/cf-ops-automation/pull/149)
+
+## [v2.1.0](https://github.com/orange-cloudfoundry/cf-ops-automation/tree/v2.1.0) (2018-06-20)
+[Full Changelog](https://github.com/orange-cloudfoundry/cf-ops-automation/compare/v1.9.1...v2.1.0)
+
+**Implemented enhancements:**
+
+- offer a preview in logs of interpolated \(manifest + operators + vars\) [\#52](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/52)
+- Add delete lifecycle [\#4](https://github.com/orange-cloudfoundry/cf-ops-automation/issues/4)
 
 **Merged pull requests:**
 

docs/features/features.html

@@ -472,10 +472,7 @@
 <span class="linenum">54</span>But("needs documentation") do
 <span class="offending"><span class="linenum">55</span>  pending</span>
 <span class="linenum">56</span>end
-<span class="linenum">57</span><span class="comment"># gem install syntax to get syntax highlighting</span></code></pre></li> <script type="text/javascript">moveProgressBar('100.0');</script><script>makeYellow('cucumber-header');makeYellow('scenario_1');</script><li id='' class='step undefined'><div class="step_name"><span class="keyword">Then </span><span class="step val">the following environment variables exist:</span></div><div class="step_file"><span>features/cf_app_deployment_environment_variable_available.feature:11</span></div><table><tr class='step' id='row_12'><td id="row_12_0" class="step skipped"><div><span class="step param">name</span></div></td><td id="row_12_1" class="step skipped"><div><span class="step param">description</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_13'><td id="row_13_0" class="step skipped"><div><span class="step param">GENERATE_DIR</span></div></td><td id="row_13_1" class="step skipped"><div><span class="step param">directory holding generated files. It's an absolute path.</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_14'><td id="row_14_0" class="step skipped"><div><span class="step param">BASE_TEMPLATE_DIR</span></div></td><td id="row_14_1" class="step skipped"><div><span class="step param">directory where `pre-cf-push.sh` is located. It's an relative path.</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_15'><td id="row_15_0" class="step skipped"><div><span class="step param">SECRETS_DIR</span></div></td><td id="row_15_1" class="step skipped"><div><span class="step param">directory holding secrets related to current deployment. It's an relative path.</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_16'><td id="row_16_0" class="step skipped"><div><span class="step param">CF_API_URL</span></div></td><td id="row_16_1" class="step skipped"><div><span class="step param">current application Cloud Foundry API url</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_17'><td id="row_17_0" class="step skipped"><div><span class="step param">CF_USERNAME</span></div></td><td id="row_17_1" class="step skipped"><div><span class="step param">current Cloud Foundry application user</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_18'><td id="row_18_0" class="step skipped"><div><span class="step param">CF_PASSWORD</span></div></td><td id="row_18_1" class="step skipped"><div><span class="step param">current Cloud Foundry application user password</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_19'><td id="row_19_0" class="step skipped"><div><span class="step param">CF_ORG</span></div></td><td id="row_19_1" class="step skipped"><div><span class="step param">current Cloud Foundry application organization</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_20'><td id="row_20_0" class="step skipped"><div><span class="step param">CF_SPACE</span></div></td><td id="row_20_1" class="step skipped"><div><span class="step param">current Cloud Foundry application space</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_21'><td id="row_21_0" class="step skipped"><div><span class="step param">CUSTOM_SCRIPT_DIR</span></div></td><td id="row_21_1" class="step skipped"><div><span class="step param">TODO</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script><tr class='step' id='row_22'><td id="row_22_0" class="step skipped"><div><span class="step param">CF_MANIFEST</span></div></td><td id="row_22_1" class="step skipped"><div><span class="step param">TODO</span></div></td></tr> <script type="text/javascript">moveProgressBar('100.0');</script></table><pre>Then("the following environment variables exist:") do |table|
-  # table is a Cucumber::MultilineArgument::DataTable
-  pending # Write code here that turns the phrase above into concrete actions
-end</pre></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div></div><div class="feature"><h2><span class="val">Feature: Creating pipelines with the COA engine</span></h2><p class="narrative">As a paas-template user,<br/>In order to deploy a pipeline with the COA engine<br/>I want to know the structure of the repos and the file content I need to feed to COA to produce pipelines<br/></p><div class="background"><h3 id="background_1"><span class="keyword">Background</span> <span class="val"></span></h3><ol><li id='' class='step passed'><div class="step_name"><span class="keyword">Given </span><span class="step val">a config repository called <span class="param">&quot;config_repository&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:4</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">And </span><span class="step val">a template repository called <span class="param">&quot;template_repository&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:8</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div><div class='scenario'><span class="scenario_file">features/generating_pipelines_with_coa.feature:10</span><h3 id="scenario_2"><span class="keyword">Scenario:</span> <span class="val">Creating sample pipelines for 'Hello World' root deployment
+<span class="linenum">57</span><span class="comment"># gem install syntax to get syntax highlighting</span></code></pre></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div></div><div class="feature"><h2><span class="val">Feature: Creating pipelines with the COA engine</span></h2><p class="narrative">As a paas-template user,<br/>In order to deploy a pipeline with the COA engine<br/>I want to know the structure of the repos and the file content I need to feed to COA to produce pipelines<br/></p><div class="background"><h3 id="background_1"><span class="keyword">Background</span> <span class="val"></span></h3><ol><li id='' class='step passed'><div class="step_name"><span class="keyword">Given </span><span class="step val">a config repository called <span class="param">&quot;config_repository&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:4</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">And </span><span class="step val">a template repository called <span class="param">&quot;template_repository&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:8</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div><div class='scenario'><span class="scenario_file">features/generating_pipelines_with_coa.feature:10</span><h3 id="scenario_2"><span class="keyword">Scenario:</span> <span class="val">Creating sample pipelines for 'Hello World' root deployment
     As a paas-template-user</span></h3><ol><li id='' class='step passed'><div class="step_name"><span class="keyword">When </span><span class="step val">I deploy <span class="param">&quot;hello-world-root-depls&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:23</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">And </span><span class="step val">with the structures shown in <span class="param">&quot;docs/reference_dataset/hello-world-root-depls.md&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:27</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">Then </span><span class="step val">the COA creates a set of deployment pipelines</span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:37</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">And </span><span class="step val">generated pipelines are valid concourse pipelines</span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:45</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div><div class='scenario'><span class="scenario_file">features/generating_pipelines_with_coa.feature:17</span><h3 id="scenario_3"><span class="keyword">Scenario:</span> <span class="val">Creating a set of empty pipelines for 'another world' root deployment
     As a paas-template-user</span></h3><ol><li id='' class='step passed'><div class="step_name"><span class="keyword">When </span><span class="step val">I deploy <span class="param">&quot;another-world-root-depls&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:23</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">And </span><span class="step val">with the structures shown in <span class="param">&quot;docs/reference_dataset/another-world-root-depls.md&quot;</span></span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:27</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">Then </span><span class="step val">the COA creates a set of deployment pipelines</span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:37</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script><li id='' class='step passed'><div class="step_name"><span class="keyword">And </span><span class="step val">generated pipelines are valid concourse pipelines</span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:45</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div></div><div class="feature"><h2><span class="val">Feature: Iaas specific support</span></h2><p class="narrative">In order to support iaas specific features<br/>As a paas-template user,<br/>I want to know mechanisms provided by COA<br/></p><div class="background"><h3 id="background_3"><span class="keyword">Background</span> <span class="val"></span></h3><ol><li id='' class='step passed'><div class="step_name"><span class="keyword">Given </span><span class="step val">Hello world generated pipelines from reference_dataset</span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:12</span></div></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div><div class='scenario'><span class="scenario_file">features/iaas_specific_support.feature:9</span><h3 id="scenario_4"><span class="keyword">Scenario:</span> <span class="val">Terraform iaas specific</span></h3><ol><script>makeYellow('cucumber-header');makeYellow('scenario_4');</script><li id='' class='step pending'><div class="step_name"><span class="keyword">But </span><span class="step val">needs documentation</span></div><div class="step_file"><span>features/step_definitions/pipeline_generation.rb:54</span></div><div class="message"><pre>TODO (Cucumber::Pending)</pre></div><div class="backtrace"><pre>./features/step_definitions/pipeline_generation.rb:55:in `"needs documentation"'
 features/iaas_specific_support.feature:10:in `But needs documentation'</pre></div><pre class="ruby"><code><span class="linenum">53</span>
@@ -524,4 +521,4 @@
 <span class="linenum">54</span>But("needs documentation") do
 <span class="offending"><span class="linenum">55</span>  pending</span>
 <span class="linenum">56</span>end
-<span class="linenum">57</span><span class="comment"># gem install syntax to get syntax highlighting</span></code></pre></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div></div><script type="text/javascript">document.getElementById('duration').innerHTML = "Finished in <strong>0m6.933s seconds</strong>";</script><script type="text/javascript">document.getElementById('totals').innerHTML = "12 scenarios (10 pending, 2 passed)<br />33 steps (1 undefined, 10 pending, 22 passed)";</script></div></body></html>
+<span class="linenum">57</span><span class="comment"># gem install syntax to get syntax highlighting</span></code></pre></li> <script type="text/javascript">moveProgressBar('100.0');</script></ol></div></div><script type="text/javascript">document.getElementById('duration').innerHTML = "Finished in <strong>0m5.657s seconds</strong>";</script><script type="text/javascript">document.getElementById('totals').innerHTML = "12 scenarios (10 pending, 2 passed)<br />32 steps (10 pending, 22 passed)";</script></div></body></html>

docs/features/features.md

@@ -11,18 +11,6 @@ Feature: Cf application deployment support
       TODO (Cucumber::Pending)
       ./features/step_definitions/pipeline_generation.rb:55:in `"needs documentation"'
       features/cf_app_deployment_environment_variable_available.feature:10:in `But needs documentation'
-    Then the following environment variables exist:
-      | name              | description                                                                     |
-      | GENERATE_DIR      | directory holding generated files. It's an absolute path.                       |
-      | BASE_TEMPLATE_DIR | directory where `pre-cf-push.sh` is located. It's an relative path.             |
-      | SECRETS_DIR       | directory holding secrets related to current deployment. It's an relative path. |
-      | CF_API_URL        | current application Cloud Foundry API url                                       |
-      | CF_USERNAME       | current Cloud Foundry application user                                          |
-      | CF_PASSWORD       | current Cloud Foundry application user password                                 |
-      | CF_ORG            | current Cloud Foundry application organization                                  |
-      | CF_SPACE          | current Cloud Foundry application space                                         |
-      | CUSTOM_SCRIPT_DIR | TODO                                                                            |
-      | CF_MANIFEST       | TODO                                                                            |
 
 Feature: Creating pipelines with the COA engine
   As a paas-template user,
@@ -134,13 +122,5 @@ Feature: Terraform support for root deployment
       features/terraform_support_for_root_deployment.feature:10:in `But needs documentation'
 
 12 scenarios (10 pending, 2 passed)
-33 steps (1 undefined, 10 pending, 22 passed)
-0m6.896s
-
-You can implement step definitions for undefined steps with these snippets:
-
-Then("the following environment variables exist:") do |table|
-  # table is a Cucumber::MultilineArgument::DataTable
-  pending # Write code here that turns the phrase above into concrete actions
-end
-
+32 steps (10 pending, 22 passed)
+0m5.585s