/
model_inline_response_200_5.go
152 lines (127 loc) · 6.9 KB
/
model_inline_response_200_5.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
/*
* AppGate SDP Controller REST API
*
* # About This specification documents the REST API calls for the AppGate SDP Controller. Please refer to the Integration chapter in the manual or contact AppGate support with any questions about this functionality. # Getting Started Requirements for API scripting: - Access to the peer interface (default port 444) of a Controller appliance. (https://sdphelp.appgate.com/adminguide/appliances-configure.html?anchor=peer) - An API user with relevant permissions. (https://sdphelp.appgate.com/adminguide/administrative-roles-configure.html) - In order to use the simple login API, Admin MFA must be disabled or the API user must be excluded. (https://sdphelp.appgate.com/adminguide/mfa-for-admins.html) # Base path HTTPS requests must be sent to the Peer Interface hostname and port, with **_/admin** path. For example: **https://appgate.company.com:444/admin** All requests must have the **Accept** header as: **application/vnd.appgate.peer-v13+json** # API Conventions API conventions are important to understand and follow strictly. - While updating objects (via PUT), entire object must be sent with all fields. - For example, if in order to add a remedy method to the condition below: ``` { \"id\": \"12699e27-b584-464a-81ee-5b4784b6d425\", \"name\": \"Test\", \"notes\": \"Making a point\", \"tags\": [\"test\", \"tag\"], \"expression\": \"return true;\", \"remedyMethods\": [] } ``` - send the entire object with updated and non-updated fields: ``` { \"id\": \"12699e27-b584-464a-81ee-5b4784b6d425\", \"name\": \"Test\", \"notes\": \"Making a point\", \"tags\": [\"test\", \"tag\"], \"expression\": \"return true;\", \"remedyMethods\": [{\"type\": \"DisplayMessage\", \"message\": \"test message\"}] } ``` - In case Controller returns an error (non-2xx HTTP status code), response body is JSON. The \"message\" field contains information about the error. HTTP 422 \"Unprocessable Entity\" has extra `errors` field to list all the issues with specific fields. - Empty string (\"\") is considered a different value than \"null\" or field being omitted from JSON. Omitting the field is recommend if no value is intended. Empty string (\"\") will be almost always rejected as invalid value. - There are common pattern between many objects: - **Configuration Objects**: There are many objects with common fields, namely \"id\", \"name\", \"notes\", \"created\" and \"updated\". These entities are listed, queried, created, updated and deleted in a similar fashion. - **Distinguished Name**: Users and Devices are identified with what is called Distinguished Names, as used in LDAP. The distinguished format that identifies a device and a user combination is \"CN=\\<Device ID\\>,CN=\\<username\\>,OU=\\<Identity Provider Name\\>\". Some objects have the \"userDistinguishedName\" field, which does not include the CN for Device ID. This identifies a user on every device.
*
* API version: API version 13
* Contact: appgatesdp.support@appgate.com
*/
// Code generated by OpenAPI Generator (https://openapi-generator.tech); DO NOT EDIT.
package openapi
import (
"encoding/json"
)
// InlineResponse2005 struct for InlineResponse2005
type InlineResponse2005 struct {
// Whether the connection succeeded or not.
Success *bool `json:"success,omitempty"`
// The error text if the connection fails.
Error *bool `json:"error,omitempty"`
}
// NewInlineResponse2005 instantiates a new InlineResponse2005 object
// This constructor will assign default values to properties that have it defined,
// and makes sure properties required by API are set, but the set of arguments
// will change when the set of required properties is changed
func NewInlineResponse2005() *InlineResponse2005 {
this := InlineResponse2005{}
return &this
}
// NewInlineResponse2005WithDefaults instantiates a new InlineResponse2005 object
// This constructor will only assign default values to properties that have it defined,
// but it doesn't guarantee that properties required by API are set
func NewInlineResponse2005WithDefaults() *InlineResponse2005 {
this := InlineResponse2005{}
return &this
}
// GetSuccess returns the Success field value if set, zero value otherwise.
func (o *InlineResponse2005) GetSuccess() bool {
if o == nil || o.Success == nil {
var ret bool
return ret
}
return *o.Success
}
// GetSuccessOk returns a tuple with the Success field value if set, nil otherwise
// and a boolean to check if the value has been set.
func (o *InlineResponse2005) GetSuccessOk() (*bool, bool) {
if o == nil || o.Success == nil {
return nil, false
}
return o.Success, true
}
// HasSuccess returns a boolean if a field has been set.
func (o *InlineResponse2005) HasSuccess() bool {
if o != nil && o.Success != nil {
return true
}
return false
}
// SetSuccess gets a reference to the given bool and assigns it to the Success field.
func (o *InlineResponse2005) SetSuccess(v bool) {
o.Success = &v
}
// GetError returns the Error field value if set, zero value otherwise.
func (o *InlineResponse2005) GetError() bool {
if o == nil || o.Error == nil {
var ret bool
return ret
}
return *o.Error
}
// GetErrorOk returns a tuple with the Error field value if set, nil otherwise
// and a boolean to check if the value has been set.
func (o *InlineResponse2005) GetErrorOk() (*bool, bool) {
if o == nil || o.Error == nil {
return nil, false
}
return o.Error, true
}
// HasError returns a boolean if a field has been set.
func (o *InlineResponse2005) HasError() bool {
if o != nil && o.Error != nil {
return true
}
return false
}
// SetError gets a reference to the given bool and assigns it to the Error field.
func (o *InlineResponse2005) SetError(v bool) {
o.Error = &v
}
func (o InlineResponse2005) MarshalJSON() ([]byte, error) {
toSerialize := map[string]interface{}{}
if o.Success != nil {
toSerialize["success"] = o.Success
}
if o.Error != nil {
toSerialize["error"] = o.Error
}
return json.Marshal(toSerialize)
}
type NullableInlineResponse2005 struct {
value *InlineResponse2005
isSet bool
}
func (v NullableInlineResponse2005) Get() *InlineResponse2005 {
return v.value
}
func (v *NullableInlineResponse2005) Set(val *InlineResponse2005) {
v.value = val
v.isSet = true
}
func (v NullableInlineResponse2005) IsSet() bool {
return v.isSet
}
func (v *NullableInlineResponse2005) Unset() {
v.value = nil
v.isSet = false
}
func NewNullableInlineResponse2005(val *InlineResponse2005) *NullableInlineResponse2005 {
return &NullableInlineResponse2005{value: val, isSet: true}
}
func (v NullableInlineResponse2005) MarshalJSON() ([]byte, error) {
return json.Marshal(v.value)
}
func (v *NullableInlineResponse2005) UnmarshalJSON(src []byte) error {
v.isSet = true
return json.Unmarshal(src, &v.value)
}