All URIs are relative to https://intersight.com
| Method | HTTP request | Description |
|---|---|---|
| create_feedback_feedback_post | POST /api/v1/feedback/FeedbackPosts | Create a 'feedback.FeedbackPost' resource. |
create_feedback_feedback_post(feedback_feedback_post, opts)
Create a 'feedback.FeedbackPost' resource.
require 'time'
require 'intersight_client'
# setup authorization
IntersightClient.configure do |config|
# Configure API key authorization: cookieAuth
config.api_key['cookieAuth'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['cookieAuth'] = 'Bearer'
# Configure OAuth2 access token for authorization: oAuth2
config.access_token = 'YOUR ACCESS TOKEN'
# Configure OAuth2 access token for authorization: oAuth2
config.access_token = 'YOUR ACCESS TOKEN'
end
api_instance = IntersightClient::FeedbackApi.new
feedback_feedback_post = IntersightClient::FeedbackFeedbackPost.new({class_id: 'feedback.FeedbackPost', object_type: 'feedback.FeedbackPost'}) # FeedbackFeedbackPost | The 'feedback.FeedbackPost' resource to create.
opts = {
if_match: 'if_match_example', # String | For methods that apply server-side changes, and in particular for PUT, If-Match can be used to prevent the lost update problem. It can check if the modification of a resource that the user wants to upload will not override another change that has been done since the original resource was fetched. If the request cannot be fulfilled, the 412 (Precondition Failed) response is returned. When modifying a resource using POST or PUT, the If-Match header must be set to the value of the resource ModTime property after which no lost update problem should occur. For example, a client send a GET request to obtain a resource, which includes the ModTime property. The ModTime indicates the last time the resource was created or modified. The client then sends a POST or PUT request with the If-Match header set to the ModTime property of the resource as obtained in the GET request.
if_none_match: 'if_none_match_example' # String | For methods that apply server-side changes, If-None-Match used with the * value can be used to create a resource not known to exist, guaranteeing that another resource creation didn't happen before, losing the data of the previous put. The request will be processed only if the eventually existing resource's ETag doesn't match any of the values listed. Otherwise, the status code 412 (Precondition Failed) is used. The asterisk is a special value representing any resource. It is only useful when creating a resource, usually with PUT, to check if another resource with the identity has already been created before. The comparison with the stored ETag uses the weak comparison algorithm, meaning two resources are considered identical if the content is equivalent - they don't have to be identical byte for byte.
}
begin
# Create a 'feedback.FeedbackPost' resource.
result = api_instance.create_feedback_feedback_post(feedback_feedback_post, opts)
p result
rescue IntersightClient::ApiError => e
puts "Error when calling FeedbackApi->create_feedback_feedback_post: #{e}"
endThis returns an Array which contains the response data, status code and headers.
<Array(, Integer, Hash)> create_feedback_feedback_post_with_http_info(feedback_feedback_post, opts)
begin
# Create a 'feedback.FeedbackPost' resource.
data, status_code, headers = api_instance.create_feedback_feedback_post_with_http_info(feedback_feedback_post, opts)
p status_code # => 2xx
p headers # => { ... }
p data # => <FeedbackFeedbackPost>
rescue IntersightClient::ApiError => e
puts "Error when calling FeedbackApi->create_feedback_feedback_post_with_http_info: #{e}"
end| Name | Type | Description | Notes |
|---|---|---|---|
| feedback_feedback_post | FeedbackFeedbackPost | The 'feedback.FeedbackPost' resource to create. | |
| if_match | String | For methods that apply server-side changes, and in particular for PUT, If-Match can be used to prevent the lost update problem. It can check if the modification of a resource that the user wants to upload will not override another change that has been done since the original resource was fetched. If the request cannot be fulfilled, the 412 (Precondition Failed) response is returned. When modifying a resource using POST or PUT, the If-Match header must be set to the value of the resource ModTime property after which no lost update problem should occur. For example, a client send a GET request to obtain a resource, which includes the ModTime property. The ModTime indicates the last time the resource was created or modified. The client then sends a POST or PUT request with the If-Match header set to the ModTime property of the resource as obtained in the GET request. | [optional] |
| if_none_match | String | For methods that apply server-side changes, If-None-Match used with the * value can be used to create a resource not known to exist, guaranteeing that another resource creation didn't happen before, losing the data of the previous put. The request will be processed only if the eventually existing resource's ETag doesn't match any of the values listed. Otherwise, the status code 412 (Precondition Failed) is used. The asterisk is a special value representing any resource. It is only useful when creating a resource, usually with PUT, to check if another resource with the identity has already been created before. The comparison with the stored ETag uses the weak comparison algorithm, meaning two resources are considered identical if the content is equivalent - they don't have to be identical byte for byte. | [optional] |
cookieAuth, http_signature, oAuth2, oAuth2
- Content-Type: application/json
- Accept: application/json