nutanix_clustermgmt 0.2.1 → 0.2.2

data/Gemfile

@@ -1,9 +0,0 @@
-source 'https://rubygems.org'
-
-gemspec
-
-group :development, :test do
-  gem 'rake', '~> 13.0.1'
-  gem 'pry-byebug'
-  gem 'rubocop', '~> 0.66.0'
-end

data/bin/console

@@ -1,15 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "bundler/setup"
-require "nutanix_clustermgmt"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/openapi-generate

@@ -1,30 +0,0 @@
-#!/bin/bash
-
-if [ -z "$INPUT_SPEC_VERSION" ]; then
-  echo "ERROR: INPUT_SPEC_VERSION must be set"
-  exit 1
-fi
-
-if [ -z "$OPENAPI_GENERATOR_JAR" ]; then
-  # Detect the latest version of the openapi-generator-cli package
-  version=`wget https://repo1.maven.org/maven2/org/openapitools/openapi-generator-cli/maven-metadata.xml -O - 2>/dev/null | xq -x "//metadata/versioning/latest"`
-  OPENAPI_GENERATOR_JAR=openapi-generator-cli-$version.jar
-
-  # Download the openapi-generator-cli jar if we don't already have it locally
-  if [ ! -f "$OPENAPI_GENERATOR_JAR" ]; then
-    echo "Downloading '$OPENAPI_GENERATOR_JAR'..."
-    wget https://repo1.maven.org/maven2/org/openapitools/openapi-generator-cli/$version/$OPENAPI_GENERATOR_JAR
-  fi
-fi
-
-# Clear out any existing files in paths that are autogenerated to prevent deleted files
-# from remaining after running the generate
-rm -rf ./docs ./lib ./spec
-
-# Generate the gem from the current openapi-spec
-input_spec=https://developers.nutanix.com/api/v1/namespaces/clustermgmt/versions/$INPUT_SPEC_VERSION/yaml
-
-# Fixup issues with the generated classes
-export RUBY_POST_PROCESS_FILE="$PWD/bin/openapi-generate-ruby-post-process"
-
-java -jar $OPENAPI_GENERATOR_JAR generate --enable-post-process-file --input-spec $input_spec --skip-validate-spec --generator-name ruby --config .openapi-config.json

data/bin/openapi-generate-ruby-post-process

@@ -1,6 +0,0 @@
-#!/bin/bash
-
-SED_EXE="$([[ "$OSTYPE" == "darwin"* ]] && echo "gsed" || echo "sed")"
-
-${SED_EXE} -i 's/_UNKNOWN/UNKNOWN/g'   $1
-${SED_EXE} -i 's/_REDACTED/REDACTED/g' $1

data/nutanix_clustermgmt.gemspec

@@ -1,39 +0,0 @@
-# -*- encoding: utf-8 -*-
-
-=begin
-#Nutanix Cluster Management APIs
-
-#Manage Hosts, Clusters and other Infrastructure.
-
-The version of the OpenAPI document: 4.0.2
-
-Generated by: https://openapi-generator.tech
-Generator version: 7.9.0
-
-=end
-
-$:.push File.expand_path("../lib", __FILE__)
-require "nutanix_clustermgmt/version"
-
-Gem::Specification.new do |s|
-  s.name        = "nutanix_clustermgmt"
-  s.version     = NutanixClustermgmt::VERSION
-  s.platform    = Gem::Platform::RUBY
-  s.authors     = ["ManageIQ Developers"]
-  s.email       = [""]
-  s.homepage    = "https://openapi-generator.tech"
-  s.summary     = "Nutanix VMM API"
-  s.description = "Ruby gem for Nutanix Cluster Management APIs"
-  s.license     = "Apache-2.0"
-  s.required_ruby_version = ">= 2.7"
-  s.metadata    = {}
-
-  s.add_runtime_dependency 'typhoeus', '~> 1.0', '>= 1.0.1'
-
-  s.add_development_dependency 'rspec', '~> 3.6', '>= 3.6.0'
-
-  s.files         = `find *`.split("\n").uniq.sort.select { |f| !f.empty? }
-  s.test_files    = `find spec/*`.split("\n")
-  s.executables   = []
-  s.require_paths = ["lib"]
-end

data/spec/api/bmc_api_spec.rb

@@ -1,64 +0,0 @@
-=begin
-#Nutanix Cluster Management APIs
-
-#Manage Hosts, Clusters and other Infrastructure.
-
-The version of the OpenAPI document: 4.0.2
-
-Generated by: https://openapi-generator.tech
-Generator version: 7.17.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for NutanixClustermgmt::BmcApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'BmcApi' do
-  before do
-    # run before each test
-    @api_instance = NutanixClustermgmt::BmcApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of BmcApi' do
-    it 'should create an instance of BmcApi' do
-      expect(@api_instance).to be_instance_of(NutanixClustermgmt::BmcApi)
-    end
-  end
-
-  # unit tests for get_bmc_info
-  # Get BMC details
-  # Get BMC details of a host
-  # @param cluster_ext_id Cluster UUID
-  # @param ext_id Host UUID
-  # @param [Hash] opts the optional parameters
-  # @return [GetBmcInfo200Response]
-  describe 'get_bmc_info test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for update_bmc_info
-  # Update BMC info summary
-  # Update BMC info
-  # @param cluster_ext_id Cluster UUID
-  # @param ext_id Host UUID
-  # @param if_match The If-Match request header makes the request conditional. When not provided, the server will respond with  an HTTP-428 (Precondition Required) response code indicating that the server requires the request to be conditional. The server will allow the successful completion of PUT and PATCH operations, if the resource matches the ETag value returned to the response of a GET operation. If the conditional does not match, then an HTTP-412 (Precondition Failed) response will be returned.
-  # @param ntnx_request_id A unique identifier that is associated with each request. The provided value must be opaque and preferably in Universal Unique Identifier (UUID) format. This identifier is also used as an idempotence token for safely retrying requests in case of network errors. All the supported Nutanix API clients add this auto-generated request identifier to each request. 
-  # @param clustermgmt_v40_config_bmc_info Update BMC info body
-  # @param [Hash] opts the optional parameters
-  # @return [UpdateBmcInfo202Response]
-  describe 'update_bmc_info test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-end

data/spec/api/cluster_profiles_api_spec.rb

@@ -1,134 +0,0 @@
-=begin
-#Nutanix Cluster Management APIs
-
-#Manage Hosts, Clusters and other Infrastructure.
-
-The version of the OpenAPI document: 4.0.2
-
-Generated by: https://openapi-generator.tech
-Generator version: 7.17.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for NutanixClustermgmt::ClusterProfilesApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'ClusterProfilesApi' do
-  before do
-    # run before each test
-    @api_instance = NutanixClustermgmt::ClusterProfilesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ClusterProfilesApi' do
-    it 'should create an instance of ClusterProfilesApi' do
-      expect(@api_instance).to be_instance_of(NutanixClustermgmt::ClusterProfilesApi)
-    end
-  end
-
-  # unit tests for apply_cluster_profile
-  # Apply cluster profile
-  # Apply profile to all the attached clusters
-  # @param ext_id Cluster Profile UUID
-  # @param ntnx_request_id A unique identifier that is associated with each request. The provided value must be opaque and preferably in Universal Unique Identifier (UUID) format. This identifier is also used as an idempotence token for safely retrying requests in case of network errors. All the supported Nutanix API clients add this auto-generated request identifier to each request. 
-  # @param clustermgmt_v40_config_cluster_reference_list_spec Payload for applying profile, which will accept a list of cluster UUIDs
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :dryrun A URL query parameter that allows long running operations to execute in a dry-run mode providing ability to identify trouble spots and system failures without performing the actual operation. Additionally this mode also offers a summary snapshot of the resultant system in order to better understand how things fit together. The operation runs in dry-run mode only if the provided value is true. 
-  # @return [ApplyClusterProfile202Response]
-  describe 'apply_cluster_profile test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for create_cluster_profile
-  # Create a cluster profile
-  # Create cluster profile with the required settings
-  # @param ntnx_request_id A unique identifier that is associated with each request. The provided value must be opaque and preferably in Universal Unique Identifier (UUID) format. This identifier is also used as an idempotence token for safely retrying requests in case of network errors. All the supported Nutanix API clients add this auto-generated request identifier to each request. 
-  # @param clustermgmt_v40_config_cluster_profile The required parameters to create a cluster profile
-  # @param [Hash] opts the optional parameters
-  # @return [CreateClusterProfile202Response]
-  describe 'create_cluster_profile test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for delete_cluster_profile_by_id
-  # Delete cluster profile
-  # Delete cluster profile. Profile consist of different cluster settings like NTP, DNS etc.
-  # @param ext_id Cluster Profile UUID
-  # @param ntnx_request_id A unique identifier that is associated with each request. The provided value must be opaque and preferably in Universal Unique Identifier (UUID) format. This identifier is also used as an idempotence token for safely retrying requests in case of network errors. All the supported Nutanix API clients add this auto-generated request identifier to each request. 
-  # @param [Hash] opts the optional parameters
-  # @return [DeleteClusterProfileById202Response]
-  describe 'delete_cluster_profile_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for disassociate_cluster_from_cluster_profile
-  # Disassociate cluster from a cluster profile
-  # Disassociate cluster from a profile
-  # @param ext_id Cluster Profile UUID
-  # @param ntnx_request_id A unique identifier that is associated with each request. The provided value must be opaque and preferably in Universal Unique Identifier (UUID) format. This identifier is also used as an idempotence token for safely retrying requests in case of network errors. All the supported Nutanix API clients add this auto-generated request identifier to each request. 
-  # @param clustermgmt_v40_config_cluster_reference_list_spec Payload for disassociating clusters, which will accept a list of cluster UUIDs
-  # @param [Hash] opts the optional parameters
-  # @return [DisassociateClusterFromClusterProfile202Response]
-  describe 'disassociate_cluster_from_cluster_profile test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for get_cluster_profile_by_id
-  # Get cluster profile
-  # Get cluster profile. Profile consist of different cluster settings like NTP, DNS etc.
-  # @param ext_id Cluster Profile UUID
-  # @param [Hash] opts the optional parameters
-  # @return [GetClusterProfileById200Response]
-  describe 'get_cluster_profile_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for list_cluster_profiles
-  # List cluster profiles
-  # Fetches a list of cluster profile entities. A profile consists of different cluster settings like Network Time Protocol(NTP), Domain Name System(DNS), and so on.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page A URL query parameter that specifies the page number of the result set. It must be a positive integer between 0 and the maximum number of pages that are available for that resource. Any number out of this range might lead to no results. 
-  # @option opts [Integer] :limit A URL query parameter that specifies the total number of records returned in the result set.  Must be a positive integer between 1 and 100. Any number out of this range will lead to a validation error. If the limit is not provided, a default value of 50 records will be returned in the result set. 
-  # @option opts [String] :filter A URL query parameter that allows clients to filter a collection of resources. The expression specified with $filter is evaluated for each resource in the collection, and only items where the expression evaluates to true are included in the response. Expression specified with the $filter must conform to the [OData V4.01](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html) URL conventions. For example, filter '$filter=name eq 'karbon-ntnx-1.0' would filter the result on cluster name 'karbon-ntnx1.0', filter '$filter=startswith(name, 'C')' would filter on cluster name starting with 'C'. The filter can be applied to the following fields: - clusterCount - createTime - createdBy - driftedClusterCount - lastUpdateTime - lastUpdatedBy - name 
-  # @option opts [String] :orderby A URL query parameter that allows clients to specify the sort criteria for the returned list of objects. Resources can be sorted in ascending order using asc or descending order using desc. If asc or desc are not specified, the resources will be sorted in ascending order by default. For example, '$orderby=templateName desc' would get all templates sorted by templateName in descending order. The orderby can be applied to the following fields: - clusterCount - createTime - createdBy - driftedClusterCount - lastUpdateTime - lastUpdatedBy - name 
-  # @option opts [String] :select A URL query parameter that allows clients to request a specific set of properties for each entity or complex type. Expression specified with the $select must conform to the [OData V4.01](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html) URL conventions. If a $select expression consists of a single select item that is an asterisk (i.e., *), then all properties on the matching resource will be returned. - allowedOverrides - clusterCount - clusters - createTime - createdBy - description - driftedClusterCount - extId - lastUpdateTime - lastUpdatedBy - links - name - nameServerIpList - nfsSubnetWhitelist - ntpServerIpList - pulseStatus - rsyslogServerList - smtpServer - snmpConfig - tenantId 
-  # @return [ListClusterProfiles200Response]
-  describe 'list_cluster_profiles test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  # unit tests for update_cluster_profile_by_id
-  # Update cluster profile
-  # Update cluster profile. Profile consist of different cluster settings like NTP, DNS etc.
-  # @param ext_id Cluster Profile UUID
-  # @param if_match The If-Match request header makes the request conditional. When not provided, the server will respond with  an HTTP-428 (Precondition Required) response code indicating that the server requires the request to be conditional. The server will allow the successful completion of PUT and PATCH operations, if the resource matches the ETag value returned to the response of a GET operation. If the conditional does not match, then an HTTP-412 (Precondition Failed) response will be returned.
-  # @param ntnx_request_id A unique identifier that is associated with each request. The provided value must be opaque and preferably in Universal Unique Identifier (UUID) format. This identifier is also used as an idempotence token for safely retrying requests in case of network errors. All the supported Nutanix API clients add this auto-generated request identifier to each request. 
-  # @param clustermgmt_v40_config_cluster_profile The required parameters to update a profile
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :dryrun A URL query parameter that allows long running operations to execute in a dry-run mode providing ability to identify trouble spots and system failures without performing the actual operation. Additionally this mode also offers a summary snapshot of the resultant system in order to better understand how things fit together. The operation runs in dry-run mode only if the provided value is true. 
-  # @return [UpdateClusterProfileById202Response]
-  describe 'update_cluster_profile_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-end