Workflows, testing and fog for fog-openbebula

.github/CODEOWNERS

@@ -0,0 +1 @@
+@test-kitchen/maintainers

.github/dependabot.yml

@@ -1,7 +1,8 @@
+---
 version: 2
 updates:
-- package-ecosystem: bundler
-  directory: "/"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
+  - package-ecosystem: bundler
+    directory: "/"
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10

.github/workflows/lint.yml

@@ -0,0 +1,9 @@
+---
+name: "Test"
+
+"on":
+  pull_request:
+
+jobs:
+  lint-unit:
+    uses: test-kitchen/.github/.github/workflows/lint-unit.yml@v0.1.2

.github/workflows/publish.yml

@@ -0,0 +1,35 @@
+---
+name: release-please
+
+"on":
+  push:
+    branches: [main]
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: google-github-actions/release-please-action@v3
+        id: release
+        with:
+          release-type: ruby
+          package-name: kitchen-opennebula
+          version-file: lib/kitchen/driver/opennebula_version.rb
+          token: ${{ secrets.PORTER_GITHUB_TOKEN }}
+
+      - name: Checkout
+        uses: actions/checkout@v4
+        if: ${{ steps.release.outputs.release_created }}
+
+      - name: Build and publish to GitHub Package
+        uses: actionshub/publish-gem-to-github@main
+        if: ${{ steps.release.outputs.release_created }}
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          owner: ${{ secrets.OWNER }}
+
+      - name: Build and publish to RubyGems
+        uses: actionshub/publish-gem-to-rubygems@main
+        if: ${{ steps.release.outputs.release_created }}
+        with:
+          token: ${{ secrets.RUBYGEMS_API_KEY }}

.markdownlint.yaml

@@ -0,0 +1,9 @@
+---
+default: true
+MD013: false
+MD024: false
+MD026: false
+MD036: false
+MD012: false
+MD029: false
+MD004: false

.rubocop.yml

@@ -0,0 +1,11 @@
+---
+require:
+  - chefstyle
+
+AllCops:
+  TargetRubyVersion: 3.1
+  Include:
+    - "**/*.rb"
+  Exclude:
+    - "vendor/**/*"
+    - "spec/**/*"

CHANGELOG.md

@@ -1,3 +1,5 @@
+# kitchen-opennebula changelog
+
 ## 0.3.0
 
 * fix endless loop in passwordless sudo check

CODEOWNERS

@@ -0,0 +1 @@
+@test-kitchen/maintainers

Gemfile

@@ -1,3 +1,11 @@
 source "https://rubygems.org"
 
 gemspec
+
+group :test do
+  gem "rake", ">= 11.0"
+end
+
+group :chefstyle do
+  gem "chefstyle", "2.2.3"
+end

README.md

@@ -1,20 +1,20 @@
-# <a name="title"></a> Kitchen::Opennebula
+# Kitchen::Opennebula
 
 A Test Kitchen Driver for Opennebula.
 
-## <a name="requirements"></a> Requirements
+## Requirements
 
-This driver depends on [fog](https://github.com/fog/fog). Please note possibility that unreleased changes on master 
-branch may depend on patches that can be found at https://github.com/blackberry/fog until they are merged to upstream.
+This driver depends on [fog](https://github.com/fog/fog). Please note possibility that unreleased changes on master
+branch may depend on patches that can be found at <https://github.com/blackberry/fog> until they are merged to upstream.
 
-## <a name="installation"></a> Installation and Setup
+## Installation and Setup
 
-1. Download and install latest [ChefDK](https://downloads.chef.io/chef-dk/).
-2. Please add bin locations to your PATH:
-  * C:\opscode\chefdk\bin;C:\opscode\chefdk\embedded\bin\ (windows)
-  * /opt/chefdk/bin/:/opt/chefdk/embedded/bin (unix)
-3. Reopen console or reload your env PATH
-4. Run following command:
+- Download and install latest [ChefDK](https://downloads.chef.io/chef-dk/).
+- Please add bin locations to your PATH:
+  - C:\opscode\chefdk\bin;C:\opscode\chefdk\embedded\bin\ (windows)
+  - /opt/chefdk/bin/:/opt/chefdk/embedded/bin (unix)
+- Reopen console or reload your env PATH
+- Run following command:
     gem install kitchen-opennebula --no-user-install --no-ri --no-rdoc
 
 Please read the [config_yml_kitchen](https://docs.chef.io/config_yml_kitchen.html) page for more details.
@@ -23,145 +23,145 @@ Please read the [config_yml_kitchen](https://docs.chef.io/config_yml_kitchen.htm
 
 This driver requires an OpenNebula OS image that conforms to a number of requirements
 
-* The VM puts the ssh key defined in the SSH\_PUBLIC\_KEY context variable into `$HOME/.ssh/authorized_keys`
-* The VM ensures the user has passwordless sudo access
+- The VM puts the ssh key defined in the SSH\_PUBLIC\_KEY context variable into `$HOME/.ssh/authorized_keys`
+- The VM ensures the user has passwordless sudo access
 
-## <a name="config"></a> Configuration
+## Configuration
 
-### <a name="opennebula_endpoint"></a> opennebula\_endpoint
+### opennebula\_endpoint
 
-URL where the OpenNebula daemon is listening. The default value is taken from the ONE\_XMLRPC environment variable, 
+URL where the OpenNebula daemon is listening. The default value is taken from the ONE\_XMLRPC environment variable,
 or `http://127.0.0.1:2633/RPC2` if unset.
 
-### <a name="oneauth_file"></a> oneauth\_file
+### oneauth\_file
 
-Path to the file containing OpenNebula authentication information.  It should contain a single line stating 
-"username:password". The default value is taken from the ONE\_AUTH environment variable, or `$HOME/.one/one_auth` if 
+Path to the file containing OpenNebula authentication information.  It should contain a single line stating
+"username:password". The default value is taken from the ONE\_AUTH environment variable, or `$HOME/.one/one_auth` if
 unset.
 
-### <a name="template_name"></a> template\_name
+### template\_name
 
-Name of the VM definition file (OpenNebula template) registered with OpenNebula.  Can be used with `template_uname` or 
-`template_uid` to further restrict which template to use if multiple users have the same template name. Only one of 
+Name of the VM definition file (OpenNebula template) registered with OpenNebula.  Can be used with `template_uname` or
+`template_uid` to further restrict which template to use if multiple users have the same template name. Only one of
 `template_name` or `template_id` must be specified in the .kitchen.yml file. The default value is unset, or `nil`.
 
-### <a name="template_id"></a> template\_id
+### template\_id
 
-ID of the VM definition file (OpenNebula template) registered with OpenNebula.  Only one of `template_name` or 
+ID of the VM definition file (OpenNebula template) registered with OpenNebula.  Only one of `template_name` or
 `template_id` must be specified in the .kitchen.yml file. The default value is unset, or `nil`.
 
-### <a name="template_uname"></a> template\_uname
+### template\_uname
 
-Username who owns the VM definition file (OpenNebula template).  Can be used with `template_name` to address naming 
+Username who owns the VM definition file (OpenNebula template).  Can be used with `template_name` to address naming
 conflicts where multiple users have the same template name. The default value is unset, or `nil`.
 
-### <a name="template_uid"></a> template\_uid
+### template\_uid
 
-UID of the user who owns the VM definition file (OpenNebula template).  Can be used with `template_name` to address 
+UID of the user who owns the VM definition file (OpenNebula template).  Can be used with `template_name` to address
 naming conflicts where multiple users have the same template name. The default value is unset, or `nil`.
 
-### <a name="vm_hostname"></a> vm\_hostname
+### vm\_hostname
 
 Hostname to set for the newly created VM. The default value is `driver.instance.name`
 
-### <a name="public_key_path"></a> public\_key\_path
+### public\_key\_path
 
-Path to SSH public key to pass to the VM, to use to authenticate with `username` when logging in or converging a node. 
-The default value is `~/.ssh/id_rsa.pub`, `~/.ssh/id_dsa.pub`, `~/.ssh/identity.pub`, or `~/.ssh/id_ecdsa.pub`, 
+Path to SSH public key to pass to the VM, to use to authenticate with `username` when logging in or converging a node.
+The default value is `~/.ssh/id_rsa.pub`, `~/.ssh/id_dsa.pub`, `~/.ssh/identity.pub`, or `~/.ssh/id_ecdsa.pub`,
 whichever is present on the filesystem.
 
-### <a name="username"></a> username
+### username
 
 This is the username used for SSH authentication to the new VM. The default value is `local`.
 
-### <a name="memory"></a> memory
+### memory
 
-The amount of memory to provision for the new VM.  This parameter will override the memory settings provided in the 
+The amount of memory to provision for the new VM.  This parameter will override the memory settings provided in the
 VM template. The default value is 512MB.
 
-### <a name="user_variables"></a> user\_variables
+### user\_variables
 
-A hash of variables to pass into the "user template" section of the VM, to customize the virtual machine. The default 
+A hash of variables to pass into the "user template" section of the VM, to customize the virtual machine. The default
 value is `{}`.
 
-### <a name="context_variables"></a> context\_variables
+### context\_variables
 
-A hash of variables to pass into the "CONTEXT" section of the VM, to further customize the virtual machine. These 
-variables override any existing context variables that are provided as part of the specified VM template. The default 
+A hash of variables to pass into the "CONTEXT" section of the VM, to further customize the virtual machine. These
+variables override any existing context variables that are provided as part of the specified VM template. The default
 value is `{}`.
 
-### <a name="config-require-chef-omnibus"></a> require\_chef\_omnibus
+### mnibus"></a> require\_chef\_omnibus
 
 Determines whether or not a Chef [Omnibus package][chef_omnibus_dl] will be
 installed. There are several different behaviors available:
 
-* `true` - the latest release will be installed. Subsequent converges will skip re-installing if chef is present.
-* `latest` - the latest release will be installed. Subsequent converges will always re-install even if chef is present.
-* `<VERSION_STRING>` (ex: `10.24.0`) - the desired version string will be passed the the install.sh script. 
+- `true` - the latest release will be installed. Subsequent converges will skip re-installing if chef is present.
+- `latest` - the latest release will be installed. Subsequent converges will always re-install even if chef is present.
+- `<VERSION_STRING>` (ex: `10.24.0`) - the desired version string will be passed the the install.sh script.
 Subsequent converges will skip if the installed version and the desired version match.
-* `false` or `nil` - no chef is installed.
+- `false` or `nil` - no chef is installed.
 
 The default value is unset, or `nil`.
 
-### <a name="wait_for"></a> wait_for
+### wait_for
 
-This variable is used to override timeout for Fog's common `wait_for` method which states that it "takes a block and 
+This variable is used to override timeout for Fog's common `wait_for` method which states that it "takes a block and
 waits for either the block to return true for the object or for a timeout (defaults to 10 minutes)".
 
-### <a name="no_ssh_tcp_check"></a> no\_ssh\_tcp\_check
+### no\_ssh\_tcp\_check
 
-To avoid test-kitchen's ssh tcp check in the create phase you can set `no_ssh_tcp_check` to `true` and do single sleep 
+To avoid test-kitchen's ssh tcp check in the create phase you can set `no_ssh_tcp_check` to `true` and do single sleep
 instead. Sleep period is configured by `no_ssh_tcp_check_sleep`. The default for `no_ssh_tcp_check` is set to `false`.
 
-### <a name="no_ssh_tcp_check_sleep"></a> no\_ssh\_tcp\_check\_sleep
+### no\_ssh\_tcp\_check\_sleep
 
-This variable configures a single sleep used when `no_ssh_tcp_check` is set to `true`. The default for `no_ssh_tcp_check` 
+This variable configures a single sleep used when `no_ssh_tcp_check` is set to `true`. The default for `no_ssh_tcp_check`
 is 2 minutes.
 
-### <a name="no_passwordless_sudo_check"></a> no\_passwordless\_sudo\_check
+### no\_passwordless\_sudo\_check
 
-To avoid test-kitchen's passwordless sudo check in the create phase you can set `no_passwordless_sudo_check` to `true` 
-and do single sleep instead. Sleep period is configured by `no_passwordless_sudo_sleep`. The default for 
+To avoid test-kitchen's passwordless sudo check in the create phase you can set `no_passwordless_sudo_check` to `true`
+and do single sleep instead. Sleep period is configured by `no_passwordless_sudo_sleep`. The default for
 `no_passwordless_sudo_check` is set to `false`.
 
-### <a name="no_passwordless_sudo_sleep"></a> no\_passwordless\_sudo\_sleep
+### no\_passwordless\_sudo\_sleep
 
-This variable configures a single sleep used when `no_passwordless_sudo_check` is set to `true`. The default for 
+This variable configures a single sleep used when `no_passwordless_sudo_check` is set to `true`. The default for
 `no_passwordless_sudo_sleep` is 2 minutes.
 
-### <a name="passwordless_sudo_timeout"></a> passwordless\_sudo\_timeout
+### passwordless\_sudo\_timeout
 
-This variable configures the max timeout will wait in the create phase for passwordless sudo to be setup. The variable 
+This variable configures the max timeout will wait in the create phase for passwordless sudo to be setup. The variable
 is used when `no_passwordless_sudo_check` is set to `false`. The default for `passwordless_sudo_timeout` is 5 minutes.
 
-### <a name="passwordless_sudo_retry_interval"></a> passwordless\_sudo\_retry\_interval
+### passwordless\_sudo\_retry\_interval
 
-This variable configures retry interval in the create phase to periodically check that passwordless sudo is setup. It 
-does this until max timeout (set by `passwordless_sudo_timeout`) is reached. The variable is used when 
+This variable configures retry interval in the create phase to periodically check that passwordless sudo is setup. It
+does this until max timeout (set by `passwordless_sudo_timeout`) is reached. The variable is used when
 `no_passwordless_sudo_check` is set to `false`. The default for `passwordless_sudo_retry_interval` is 10 seconds.
 
-### <a name="cloud_init_timeout"></a> cloud\_init\_timeout
+### cloud\_init\_timeout
 
-This variable configures the max timeout Test-Kitchen will wait in the create phase for cloud-init to complete. The 
+This variable configures the max timeout Test-Kitchen will wait in the create phase for cloud-init to complete. The
 default for `cloud_init_timeout` is 10 minutes.
 
-### <a name="cloud_init_retry_interval"></a> cloud\_init\_retry\_interval
+### cloud\_init\_retry\_interval
 
-This variable configures retry interval in the create phase to periodically check that cloud-init fas finished 
-successfully. It does this until max timeout (set by `cloud_init_timeout`) is reached. The variable is used when 
+This variable configures retry interval in the create phase to periodically check that cloud-init fas finished
+successfully. It does this until max timeout (set by `cloud_init_timeout`) is reached. The variable is used when
 `no_cloud_init_check` is set to `false`. The default for `cloud_init_retry_interval` is 10 seconds.
 
-### <a name="no_cloud_init_check"></a> no\_cloud\_init\_check
+### no\_cloud\_init\_check
 
-To avoid test-kitchen to check for cloud-init completion in the create phase, you can set `no_cloud_init_check` to `true` 
-and cloud-init completion check will be ignored. If cloud-init is not used the check is skipped automatically. You could 
-use this to disable the cloud-init completion check when cloud-init is in use. The default for `no_cloud_init_check` 
+To avoid test-kitchen to check for cloud-init completion in the create phase, you can set `no_cloud_init_check` to `true`
+and cloud-init completion check will be ignored. If cloud-init is not used the check is skipped automatically. You could
+use this to disable the cloud-init completion check when cloud-init is in use. The default for `no_cloud_init_check`
 is set to `false`.
 
-## <a name="development"></a> Development
+## Development
 
-* Source hosted at [GitHub][repo]
-* Report issues/questions/feature requests on [GitHub Issues][issues]
+- Source hosted at [GitHub][repo]
+- Report issues/questions/feature requests on [GitHub Issues][issues]
 
 Pull requests are very welcome! Make sure your patches are well tested.
 Ideally create a topic branch for every separate change you make. For example:
@@ -172,15 +172,11 @@ Ideally create a topic branch for every separate change you make. For example:
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request
 
-## <a name="license"></a> License
+## License
 
 Apache 2.0 (see [LICENSE][license])
 
-
-[author]:           https://github.com/blackberry/kitchen-opennebula
-[maintainer]:       https://github.com/blackberry/kitchen-opennebula
 [issues]:           https://github.com/test-kitchen/kitchen-opennebula/issues
 [license]:          https://github.com/test-kitchen/kitchen-opennebula/blob/master/LICENSE
 [repo]:             https://github.com/test-kitchen/kitchen-opennebula
-[driver_usage]:     http://docs.kitchen-ci.org/drivers/usage
 [chef_omnibus_dl]:  http://www.getchef.com/chef/install/