knife-ionoscloud 5.0.0.beta.1 → 5.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bbe911ee22d8bcb3ce365bcbaa01e4f694f204bf87863f3b732b634bf15da4e9
-  data.tar.gz: 78618ab79c08a9a86286e0016d547f1c8e85415fe5cffde4a0de2470f33cd69b
+  metadata.gz: 9eedb6192d82af4e852eaffcbcb983097b6c754bacabc53d8ff07ca6eb05d756
+  data.tar.gz: 1d801dbb3188a4c11ea1c0af3885af541de5f2c7dd0217123a6c4b22de8c1c76
 SHA512:
-  metadata.gz: 473405e0ff5e916d40bba13014e3aa97cd44ee810e982ab809c1249122176f805429edf99cde6cce082d2e7c5b40a2838df2bd1fc068021b93aec17b86843c7e
-  data.tar.gz: a6a7a513bd6ff8f561f7000f156e93614afdc3a1cc248abd18f25973aba4a804511be8766f1b07466d1bdca8c0ca399fb4baef4122c9cf35ed691a0e0de35e3c
+  metadata.gz: a34bce481fb7c206d434f148dbf4e6192a7f4c30186802bae6bcae66b2208179bfebbd046de5f8fe8fc1bc4d9f3ffb2c086f2f0d4e90246da185ec2c063df117
+  data.tar.gz: ead0faec57ba79805bff579593099ba13ab0a49366299f89d0d2b8df2f11c93da85f6ae6f105697918a26b5e49a7396c3791e60e60649c1c168e26fc75dbc7f0

data/.github/workflows/build.yml

@@ -0,0 +1,20 @@
+name: Build
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    types: [opened, synchronize, reopened]
+jobs:
+  sonarcloud:
+    name: SonarCloud
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: 0  # Shallow clones should be disabled for a better relevancy of analysis
+      - name: SonarCloud Scan
+        uses: SonarSource/sonarcloud-github-action@master
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Needed to get PR information, if any
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

data/.github/workflows/ci.yml

@@ -11,10 +11,10 @@ on:
 
 jobs:
   test:
-    env:
-      ruby-version: 2.7
-
     runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        ruby-version: [ 2.6, 2.7, 3.0 ]
 
     steps:
       - name: Checkout
@@ -23,7 +23,7 @@ jobs:
       - name: Setup Ruby
         uses: ruby/setup-ruby@v1.61.1
         with:
-          ruby-version: ${{ env.ruby-version }}
+          ruby-version: ${{ matrix.ruby-version }}
 
       - name: Install Rubocop
         run: gem install rubocop

data/.github/workflows/publish.yml

@@ -3,11 +3,9 @@
 name: Publish
 
 on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version to publish (e.g. v1.2.3)'
-        required: true
+  push:
+    tags:
+      - 'v*'
 
 jobs:
   publish:
@@ -19,15 +17,9 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v2
-
-      - name: Validate the version
-        shell: bash
-        run: |
-          if [ "${{ github.event.inputs.version }}" != cat lib/knife-ionoscloud/version.rb | grep 'VERSION =' | tr -s ' ' | cut -d ' ' -f 4 | sed 's/^.//;s/.$//' ]; then
-            echo "Specified version does not match the one from version.rb!"
-            exit 1
-          fi
-          echo Next version will be: v${{ github.event.inputs.version }}
+      
+      - name: Unshallow
+        run: git fetch --prune --unshallow
 
       - name: Setup Ruby
         uses: ruby/setup-ruby@v1.61.1
@@ -46,6 +38,24 @@ jobs:
       - name: Run the tests
         run: rspec
 
+      - name: Get the new version
+        id: new_version
+        run: echo ::set-output name=VERSION::$(git tag --list "v*" --sort=version:refname | tail -n 1)
+
+      - name: Get the old version
+        id: old_version
+        run: echo ::set-output name=VERSION::$(git tag --list "v*" --sort=version:refname | tail -n 2 | head -n 1)
+
+      - name: Get the release version
+        run: echo "RELEASE_VERSION=${GITHUB_REF:10}" >> $GITHUB_ENV
+
+      - name: Check Version
+        run: |
+          if [ $RELEASE_VERSION != v$(cat lib/knife-ionoscloud/version.rb | grep 'VERSION =' | tr -s ' ' | cut -d ' ' -f 4 | sed 's/^.//;s/.$//') ]; then
+            echo "Tag version does not match the one from version.rb!"
+            exit 1
+          fi
+
       - name: Create RubyGems release of the Knife plugin
         shell: bash
         run: |
@@ -56,3 +66,7 @@ jobs:
           EOF
           chmod 0600 ~/.gem/credentials
           gem push $(gem build knife-ionoscloud.gemspec | grep 'File' | tr -s ' ' | cut -d ' ' -f 3)
+
+      - name: Check version and create GitHub branch
+        run: |
+          /usr/bin/bash ./git-versioning.sh ${{ steps.new_version.outputs.VERSION }} ${{ steps.old_version.outputs.VERSION }}

data/.rubocop.yml

@@ -1,7 +1,6 @@
 # This file is based on https://github.com/rails/rails/blob/master/.rubocop.yml (MIT license)
 # Automatically generated by OpenAPI Generator (https://openapi-generator.tech)
 AllCops:
-  TargetRubyVersion: 2.4
   # RuboCop has a bunch of cops enabled by default. This setting tells RuboCop
   # to ignore them, so only the ones explicitly set in this file are enabled.
   DisabledByDefault: true

data/README.md

@@ -0,0 +1,81 @@
+# Knife Plugin for IONOS Cloud
+
+![CI](https://github.com/ionos-cloud/knife-ionos-cloud/workflows/CI/badge.svg) 
+[![Gem Version](https://badge.fury.io/rb/knife-ionoscloud.svg)](https://badge.fury.io/rb/knife-ionoscloud) 
+[![Gitter](https://badges.gitter.im/ionos-cloud/sdk-general.png)](https://gitter.im/ionos-cloud/sdk-general)
+[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=knife-plugin&metric=alert_status)](https://sonarcloud.io/dashboard?id=knife-plugin)
+[![Bugs](https://sonarcloud.io/api/project_badges/measure?project=knife-plugin&metric=bugs)](https://sonarcloud.io/dashboard?id=knife-plugin)
+[![Maintainability Rating](https://sonarcloud.io/api/project_badges/measure?project=knife-plugin&metric=sqale_rating)](https://sonarcloud.io/dashboard?id=knife-plugin)
+[![Reliability Rating](https://sonarcloud.io/api/project_badges/measure?project=knife-plugin&metric=reliability_rating)](https://sonarcloud.io/dashboard?id=knife-plugin)
+[![Security Rating](https://sonarcloud.io/api/project_badges/measure?project=knife-plugin&metric=security_rating)](https://sonarcloud.io/dashboard?id=knife-plugin)
+[![Vulnerabilities](https://sonarcloud.io/api/project_badges/measure?project=knife-plugin&metric=vulnerabilities)](https://sonarcloud.io/dashboard?id=knife-plugin)
+
+## Overview
+
+Chef is a popular configuration management tool that allows simplified configuration and maintenance of both servers and cloud provider environments through the use of common templates called recipes. The Chef `knife` command line tool allows management of various nodes within those environments. The `knife-ionoscloud` plugin utilizes the IONOS Cloud REST API to provision and manage various cloud resources on the IONOS Cloud platform.
+
+In depth documaentation can be found at [here](https://docs.ionos.com/knife-plugin).
+
+
+## Getting Started
+
+An IONOS account is required for access to the Cloud API; credentials from your registration are used to authenticate against the IONOS Cloud API.
+
+### Installation
+
+The `knife-ionoscloud` plugin can be installed as a gem:
+
+```text
+$ gem install knife-ionoscloud
+```
+
+Or the plugin can be installed by adding the following line to your application's Gemfile:
+
+```text
+gem 'knife-ionoscloud'
+```
+
+And then execute:
+
+```text
+$ bundle
+```
+
+### Configuration
+
+The Ionoscloud account credentials can be added to the `knife.rb` configuration file.
+
+```text
+knife[:ionoscloud_username] = 'username'
+knife[:ionoscloud_password] = 'password'
+```
+
+If a virtual data center has already been created under the Ionoscloud account, then the data center UUID can be added to the `knife.rb` which reduces the need to include the `--datacenter-id [datacenter_id]` parameter for each action within the data center.
+
+```text
+knife[:datacenter_id] = 'f3f3b6fe-017d-43a3-b42a-a759144b2e99'
+
+knife[:ionoscloud_debug] = true
+```
+
+The configuration parameters can also be passed using shell environment variables. First, the following should be added to the `knife.rb` configuration file:
+
+```text
+knife[:ionoscloud_username] = ENV['IONOSCLOUD_USERNAME']
+knife[:ionoscloud_password] = ENV['IONOSCLOUD_PASSWORD']
+```
+
+Now the parameters can be set as environment variables:
+
+```text
+$ export IONOSCLOUD_USERNAME='username'
+$ export IONOSCLOUD_PASSWORD='password'
+```
+
+### Testing
+
+```text
+$ rspec spec
+```
+
+Bugs & feature requests can be open on the repository issues: [https://github.com/ionos-cloud/knife-ionos-cloud/issues/new/choose](https://github.com/ionos-cloud/knife-ionos-cloud/issues/new/choose)

data/docs/README.md

@@ -1,57 +1,90 @@
-# Ionoscloud Chef Knife Plugin
+# Introduction
 
-![CI](https://github.com/ionos-cloud/knife-ionos-cloud/workflows/CI/badge.svg)
-[![Gem Version](https://badge.fury.io/rb/knife-ionoscloud.svg)](https://badge.fury.io/rb/knife-ionoscloud)
-[![Gitter](https://badges.gitter.im/ionos-cloud/sdk-general.png)](https://gitter.im/ionos-cloud/sdk-general)
+![CI](https://github.com/ionos-cloud/knife-ionos-cloud/workflows/CI/badge.svg) [![Gem Version](https://badge.fury.io/rb/knife-ionoscloud.svg)](https://badge.fury.io/rb/knife-ionoscloud) [![Gitter](https://badges.gitter.im/ionos-cloud/sdk-general.png)](https://gitter.im/ionos-cloud/sdk-general)
 
 ## Overview
 
-Chef is a popular configuration management tool that allows simplified configuration and maintenance of both servers and cloud provider environments through the use of common templates called recipes. The Chef `knife` command line tool allows management of various nodes within those environments. The `knife-ionoscloud` plugin utilizes the Ionoscloud REST API to provision and manage various cloud resources on the Ionoscloud platform.
+Chef is a popular configuration management tool that allows simplified configuration and maintenance of both servers and cloud provider environments through the use of common templates called recipes. The Chef `knife` command line tool allows management of various nodes within those environments. The `knife-ionoscloud` plugin utilizes the IONOS Cloud REST API to provision and manage various cloud resources on the IONOS Cloud platform.
 
 ## Getting Started
 
-Before you begin you will need to have [signed-up](https://www.ionos.com/enterprise-cloud/signup) for a Ionoscloud account. The credentials you establish during sign-up will be used to authenticate against the [Ionoscloud Cloud API](https://devops.ionos.com/api/).
+An IONOS account is required for access to the Cloud API; credentials from your registration are used to authenticate against the IONOS Cloud API.
 
 ### Installation
 
 The `knife-ionoscloud` plugin can be installed as a gem:
 
-    $ gem install knife-ionoscloud
+```text
+$ gem install knife-ionoscloud
+```
 
 Or the plugin can be installed by adding the following line to your application's Gemfile:
 
-    gem 'knife-ionoscloud'
+```text
+gem 'knife-ionoscloud'
+```
 
 And then execute:
 
-    $ bundle
+```text
+$ bundle
+```
 
 ### Configuration
 
 The Ionoscloud account credentials can be added to the `knife.rb` configuration file.
 
-    knife[:ionoscloud_username] = 'username'
-    knife[:ionoscloud_password] = 'password'
+```text
+knife[:ionoscloud_username] = 'username'
+knife[:ionoscloud_password] = 'password'
+```
 
 If a virtual data center has already been created under the Ionoscloud account, then the data center UUID can be added to the `knife.rb` which reduces the need to include the `--datacenter-id [datacenter_id]` parameter for each action within the data center.
 
-    knife[:datacenter_id] = 'f3f3b6fe-017d-43a3-b42a-a759144b2e99'
+```text
+knife[:datacenter_id] = 'f3f3b6fe-017d-43a3-b42a-a759144b2e99'
 
-    knife[:ionoscloud_debug] = true
+knife[:ionoscloud_debug] = true
+```
 
 The configuration parameters can also be passed using shell environment variables. First, the following should be added to the `knife.rb` configuration file:
 
-    knife[:ionoscloud_username] = ENV['IONOSCLOUD_USERNAME']
-    knife[:ionoscloud_password] = ENV['IONOSCLOUD_PASSWORD']
+```text
+knife[:ionoscloud_username] = ENV['IONOSCLOUD_USERNAME']
+knife[:ionoscloud_password] = ENV['IONOSCLOUD_PASSWORD']
+```
 
 Now the parameters can be set as environment variables:
 
-    $ export IONOSCLOUD_USERNAME='username'
-    $ export IONOSCLOUD_PASSWORD='password'
+```text
+$ export IONOSCLOUD_USERNAME='username'
+$ export IONOSCLOUD_PASSWORD='password'
+```
 
 ### Testing
 
-    $ rspec spec
+```text
+$ rspec spec
+```
+
+### Getting input from a file
+
+In order to make passing JSON or array arguments easier, we allow you to specify a file which holds the arguments for a command. This is done with the `--extra-config EXTRA_CONFIG_FILE_PATH` or `-e EXTRA_CONFIG_FILE_PATH`. The file is expected to contain a JSON which should map the name of arguments to their expected values. Here is an example of such a file.
+
+```javascript
+{
+  "ionoscloud_username": "username",
+  "ionoscloud_password": "password",
+  "name": "test_datacenter_name",
+  "location": "de/txl"
+}
+```
+
+When using the command `knife ionoscloud datacenter create --extra-config EXTRA_CONFIG_FILE_PATH` where EXTRA\_CONFIG\_FILE\_PATH is the name of the file containing the JSON above, the arguments described in the file will be used.
+
+* If any of the arguments are set in any other way, the values from the file will be ignored. Running the command `knife ionoscloud datacenter create --location us/las --extra-config EXTRA_CONFIG_FILE_PATH` will create a datacenter in the 'us/las' location. In the same way if the values for ionoscloud\_username and ionoscloud\_password are already set in the knife.rb file, the contents from the JSON will be ignored.
+* Only Ionoscloud specific options may be altered using this option.
+* If an option is ignored because it is not on the available options list or if it is overwritten in another way then a warning message will be displayed.
 
 ## Feature Reference
 
@@ -65,3 +98,4 @@ The IONOS Cloud plugin for Knife aims to offer access to all resources in the IO
 1. How can I open a bug/feature request?
 
 Bugs & feature requests can be open on the repository issues: [https://github.com/ionos-cloud/knife-ionos-cloud/issues/new/choose](https://github.com/ionos-cloud/knife-ionos-cloud/issues/new/choose)
+

data/docs/changelog.md

@@ -1 +1,2 @@
-# CHANGELOG
+# Changelog
+

data/docs/docs_generator.rb

@@ -49,7 +49,7 @@ def generate_subcommand_doc(subcommand)
     value[:required] = subcommand.required_options.include? key
     value[:description][0] = value[:description][0].downcase
     value
-  }.rotate(2)
+  }.rotate(3)
 
   subcommand_name = subcommand.class.to_s
   subcommand_name.slice!('Chef::Knife::Ionoscloud')
@@ -69,7 +69,7 @@ def generate_subcommand_doc(subcommand)
         options,
         description,
         subcommand_name,
-        subcommand.required_options,
+        subcommand.required_options.map { |el| el.to_s.gsub '_', '\_' },
       ).render,
     )
   }

data/docs/subcommands/backupunit_create.md

@@ -2,27 +2,28 @@
 
 Create a new backup unit.
 
-    knife ionoscloud backupunit create (options)
-
+```text
+knife ionoscloud backupunit create (options)
+```
 
 ## Available options:
----
 
 ### Required options:
+
 * name
 * password
 * email
-* ionoscloud_username
-* ionoscloud_password
+* ionoscloud\_username
+* ionoscloud\_password
 
-```
+```text
     name: --name NAME, -n NAME
         alphanumeric name you want assigned to the backup unit (required)
 
     password: --password PASSWORD, -p PASSWORD
         alphanumeric password you want assigned to the backup unit (required)
 
-    email: --email EMAIL, -e EMAIL
+    email: --email EMAIL
         the e-mail address you want assigned to the backup unit. (required)
 
     ionoscloud_username: --username USERNAME, -u USERNAME
@@ -31,8 +32,12 @@ Create a new backup unit.
     ionoscloud_password: --password PASSWORD, -p PASSWORD
         your Ionoscloud password (required)
 
-```
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
 
+```
 ## Example
 
-    knife ionoscloud backupunit create --name NAME --password PASSWORD --email EMAIL --username USERNAME --password PASSWORD
+```text
+knife ionoscloud backupunit create --name NAME --password PASSWORD --email EMAIL --username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```

data/docs/subcommands/backupunit_delete.md

@@ -2,25 +2,30 @@
 
 A backup unit may be deleted using a DELETE request. Deleting a backup unit is a dangerous operation. A successful DELETE request will remove the backup plans inside a backup unit, ALL backups associated with the backup unit, the backup user and finally the backup unit itself.
 
-    knife ionoscloud backupunit delete BACKUPUNIT_ID [BACKUPUNIT_ID]
-
+```text
+knife ionoscloud backupunit delete BACKUPUNIT_ID [BACKUPUNIT_ID]
+```
 
 ## Available options:
----
 
 ### Required options:
-* ionoscloud_username
-* ionoscloud_password
 
-```
+* ionoscloud\_username
+* ionoscloud\_password
+
+```text
     ionoscloud_username: --username USERNAME, -u USERNAME
         your Ionoscloud username (required)
 
     ionoscloud_password: --password PASSWORD, -p PASSWORD
         your Ionoscloud password (required)
 
-```
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
 
+```
 ## Example
 
-    knife ionoscloud backupunit delete BACKUPUNIT_ID [BACKUPUNIT_ID]--username USERNAME --password PASSWORD
+```text
+knife ionoscloud backupunit delete BACKUPUNIT_ID [BACKUPUNIT_ID]--username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```

data/docs/subcommands/backupunit_get.md

@@ -0,0 +1,35 @@
+# BackupunitGet
+
+Retrieves information about a backup unit.
+
+```text
+knife ionoscloud backupunit get (options)
+```
+
+## Available options:
+
+### Required options:
+
+* backupunit\_id
+* ionoscloud\_username
+* ionoscloud\_password
+
+```text
+    backupunit_id: --backupunit-id BACKUPUNIT_ID, -B BACKUPUNIT_ID
+        the ID of the Backup unit. (required)
+
+    ionoscloud_username: --username USERNAME, -u USERNAME
+        your Ionoscloud username (required)
+
+    ionoscloud_password: --password PASSWORD, -p PASSWORD
+        your Ionoscloud password (required)
+
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
+
+```
+## Example
+
+```text
+knife ionoscloud backupunit get --backupunit-id BACKUPUNIT_ID --username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```

data/docs/subcommands/backupunit_list.md

@@ -2,25 +2,30 @@
 
 Retrieve a list of all the backup units the supplied credentials have access to.
 
-    knife ionoscloud backupunit list
-
+```text
+knife ionoscloud backupunit list
+```
 
 ## Available options:
----
 
 ### Required options:
-* ionoscloud_username
-* ionoscloud_password
 
-```
+* ionoscloud\_username
+* ionoscloud\_password
+
+```text
     ionoscloud_username: --username USERNAME, -u USERNAME
         your Ionoscloud username (required)
 
     ionoscloud_password: --password PASSWORD, -p PASSWORD
         your Ionoscloud password (required)
 
-```
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
 
+```
 ## Example
 
-    knife ionoscloud backupunit list--username USERNAME --password PASSWORD
+```text
+knife ionoscloud backupunit list--username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```

data/docs/subcommands/backupunit_ssourl.md

@@ -1,19 +1,20 @@
 # BackupunitSsourl
 
-The ProfitBricks backup system features a web-based GUI. Once you have created a backup unit, you can access the GUI with a Single Sign On (SSO) URL that can be retrieved from the Cloud API using this request.
-
-    knife ionoscloud backupunit ssourl (options)
+The ProfitBricks backup system features a web-based GUI. Once you have created a backup unit, you can access the GUI with a Single Sign On \(SSO\) URL that can be retrieved from the Cloud API using this request.
 
+```text
+knife ionoscloud backupunit ssourl (options)
+```
 
 ## Available options:
----
 
 ### Required options:
-* backupunit_id
-* ionoscloud_username
-* ionoscloud_password
 
-```
+* backupunit\_id
+* ionoscloud\_username
+* ionoscloud\_password
+
+```text
     backupunit_id: --backupunit-id BACKUPUNIT_ID, -B BACKUPUNIT_ID
         the ID of the Backup unit. (required)
 
@@ -23,8 +24,12 @@ The ProfitBricks backup system features a web-based GUI. Once you have created a
     ionoscloud_password: --password PASSWORD, -p PASSWORD
         your Ionoscloud password (required)
 
-```
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
 
+```
 ## Example
 
-    knife ionoscloud backupunit ssourl --backupunit-id BACKUPUNIT_ID --username USERNAME --password PASSWORD
+```text
+knife ionoscloud backupunit ssourl --backupunit-id BACKUPUNIT_ID --username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```

data/docs/subcommands/backupunit_update.md

@@ -0,0 +1,41 @@
+# BackupunitUpdate
+
+Retrieves information about a backup unit.
+
+```text
+knife ionoscloud backupunit update (options)
+```
+
+## Available options:
+
+### Required options:
+
+* backupunit\_id
+* ionoscloud\_username
+* ionoscloud\_password
+
+```text
+    backupunit_id: --backupunit-id BACKUPUNIT_ID, -B BACKUPUNIT_ID
+        the ID of the Backup unit. (required)
+
+    password: --password PASSWORD, -p PASSWORD
+        alphanumeric password you want assigned to the backup unit
+
+    email: --email EMAIL
+        the e-mail address you want assigned to the backup unit.
+
+    ionoscloud_username: --username USERNAME, -u USERNAME
+        your Ionoscloud username (required)
+
+    ionoscloud_password: --password PASSWORD, -p PASSWORD
+        your Ionoscloud password (required)
+
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
+
+```
+## Example
+
+```text
+knife ionoscloud backupunit update --backupunit-id BACKUPUNIT_ID --password PASSWORD --email EMAIL --username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```

data/docs/subcommands/composite_server_create.md

@@ -2,14 +2,15 @@
 
 This creates a new composite server with an attached volume and NIC in a specified virtual data center.
 
-    knife ionoscloud composite server create (options)
-
+```text
+knife ionoscloud composite server create (options)
+```
 
 ## Available options:
----
 
 ### Required options:
-* datacenter_id
+
+* datacenter\_id
 * name
 * cores
 * ram
@@ -17,10 +18,10 @@ This creates a new composite server with an attached volume and NIC in a specifi
 * type
 * dhcp
 * lan
-* ionoscloud_username
-* ionoscloud_password
+* ionoscloud\_username
+* ionoscloud\_password
 
-```
+```text
     datacenter_id: --datacenter-id DATACENTER_ID, -D DATACENTER_ID
         name of the virtual datacenter (required)
 
@@ -90,8 +91,12 @@ This creates a new composite server with an attached volume and NIC in a specifi
     ionoscloud_password: --password PASSWORD, -p PASSWORD
         your Ionoscloud password (required)
 
-```
+    extra_config_file: --extra-config EXTRA_CONFIG_FILE_PATH, -e EXTRA_CONFIG_FILE_PATH
+        path to the additional config file
 
+```
 ## Example
 
-    knife ionoscloud composite server create --datacenter-id DATACENTER_ID --name NAME --cores CORES --cpu-family CPU_FAMILY --ram RAM --availability-zone AVAILABILITY_ZONE --volume-name NAME --size SIZE --bus BUS --image ID --image-alias IMAGE_ALIAS --type TYPE --licence-type LICENCE --image-password PASSWORD --volume-availability-zone AVAILABILITY_ZONE --ssh-keys SSHKEY1,SSHKEY2,... --nic-name NAME --ips IP[,IP,...] --dhcp --lan ID --nat --username USERNAME --password PASSWORD
+```text
+knife ionoscloud composite server create --datacenter-id DATACENTER_ID --name NAME --cores CORES --cpu-family CPU_FAMILY --ram RAM --availability-zone AVAILABILITY_ZONE --volume-name NAME --size SIZE --bus BUS --image ID --image-alias IMAGE_ALIAS --type TYPE --licence-type LICENCE --image-password PASSWORD --volume-availability-zone AVAILABILITY_ZONE --ssh-keys SSHKEY1,SSHKEY2,... --nic-name NAME --ips IP[,IP,...] --dhcp --lan ID --nat --username USERNAME --password PASSWORD --extra-config EXTRA_CONFIG_FILE_PATH
+```