Skip to content

Commit 82f1654

Browse files
committed
time columns
1 parent a3e443c commit 82f1654

6 files changed

+52
-78
lines changed

model_audit_log_item_model.go

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,21 @@
11
/*
22
* ConfigCat Public Management API
33
*
4-
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
4+
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
55
*
66
* API version: v1
77
* Contact: support@configcat.com
88
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
99
*/
1010
package configcatpublicapi
11-
import (
12-
"time"
13-
)
1411

1512
type AuditLogItemModel struct {
16-
AuditLogId int64 `json:"auditLogId,omitempty"`
17-
AuditLogDateTime time.Time `json:"auditLogDateTime,omitempty"`
13+
AuditLogId int64 `json:"auditLogId,omitempty"`
1814
AuditLogType string `json:"auditLogType,omitempty"`
19-
UserEmail string `json:"userEmail,omitempty"`
20-
UserName string `json:"userName,omitempty"`
21-
Where string `json:"where,omitempty"`
22-
Why string `json:"why,omitempty"`
15+
UserEmail string `json:"userEmail,omitempty"`
16+
UserName string `json:"userName,omitempty"`
17+
Where string `json:"where,omitempty"`
18+
Why string `json:"why,omitempty"`
2319
ActionTarget string `json:"actionTarget,omitempty"`
24-
Details string `json:"details,omitempty"`
20+
Details string `json:"details,omitempty"`
2521
}

model_setting_data_model.go

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,22 @@
11
/*
22
* ConfigCat Public Management API
33
*
4-
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
4+
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
55
*
66
* API version: v1
77
* Contact: support@configcat.com
88
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
99
*/
1010
package configcatpublicapi
11-
import (
12-
"time"
13-
)
1411

1512
type SettingDataModel struct {
16-
SettingId int32 `json:"settingId,omitempty"`
17-
Key string `json:"key,omitempty"`
18-
Name string `json:"name,omitempty"`
19-
Hint string `json:"hint,omitempty"`
20-
SettingType *SettingType `json:"settingType,omitempty"`
21-
CreatedAt time.Time `json:"createdAt,omitempty"`
22-
CreatorEmail string `json:"creatorEmail,omitempty"`
23-
CreatorFullName string `json:"creatorFullName,omitempty"`
24-
OwnerFullName string `json:"ownerFullName,omitempty"`
25-
OwnerEmail string `json:"ownerEmail,omitempty"`
26-
ExpirationWarningAt time.Time `json:"expirationWarningAt,omitempty"`
13+
SettingId int32 `json:"settingId,omitempty"`
14+
Key string `json:"key,omitempty"`
15+
Name string `json:"name,omitempty"`
16+
Hint string `json:"hint,omitempty"`
17+
SettingType *SettingType `json:"settingType,omitempty"`
18+
CreatorEmail string `json:"creatorEmail,omitempty"`
19+
CreatorFullName string `json:"creatorFullName,omitempty"`
20+
OwnerFullName string `json:"ownerFullName,omitempty"`
21+
OwnerEmail string `json:"ownerEmail,omitempty"`
2722
}

model_setting_model.go

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,22 @@
11
/*
22
* ConfigCat Public Management API
33
*
4-
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
4+
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
55
*
66
* API version: v1
77
* Contact: support@configcat.com
88
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
99
*/
1010
package configcatpublicapi
11-
import (
12-
"time"
13-
)
1411

1512
type SettingModel struct {
16-
SettingId int32 `json:"settingId,omitempty"`
17-
Key string `json:"key,omitempty"`
18-
Name string `json:"name,omitempty"`
19-
Hint string `json:"hint,omitempty"`
20-
SettingType *SettingType `json:"settingType,omitempty"`
21-
OwnerUserEmail string `json:"ownerUserEmail,omitempty"`
22-
OwnerUserFullName string `json:"ownerUserFullName,omitempty"`
23-
ExpirationWarningAt time.Time `json:"expirationWarningAt,omitempty"`
24-
ConfigId string `json:"configId,omitempty"`
25-
ConfigName string `json:"configName,omitempty"`
13+
SettingId int32 `json:"settingId,omitempty"`
14+
Key string `json:"key,omitempty"`
15+
Name string `json:"name,omitempty"`
16+
Hint string `json:"hint,omitempty"`
17+
SettingType *SettingType `json:"settingType,omitempty"`
18+
OwnerUserEmail string `json:"ownerUserEmail,omitempty"`
19+
OwnerUserFullName string `json:"ownerUserFullName,omitempty"`
20+
ConfigId string `json:"configId,omitempty"`
21+
ConfigName string `json:"configName,omitempty"`
2622
}

model_setting_value_model.go

Lines changed: 9 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,23 @@
11
/*
22
* ConfigCat Public Management API
33
*
4-
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
4+
* **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). <!-- ReDoc-Inject: <security-definitions> --> # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header.
55
*
66
* API version: v1
77
* Contact: support@configcat.com
88
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
99
*/
1010
package configcatpublicapi
11-
import (
12-
"time"
13-
)
1411

1512
type SettingValueModel struct {
16-
Config *ConfigModel `json:"config,omitempty"`
17-
Environment *EnvironmentModel `json:"environment,omitempty"`
18-
ReadOnly bool `json:"readOnly,omitempty"`
19-
Setting *SettingDataModel `json:"setting,omitempty"`
20-
UpdatedAt time.Time `json:"updatedAt,omitempty"`
21-
LastUpdaterUserEmail string `json:"lastUpdaterUserEmail,omitempty"`
22-
LastUpdaterUserFullName string `json:"lastUpdaterUserFullName,omitempty"`
23-
IntegrationLinks []IntegrationLinkModel `json:"integrationLinks,omitempty"`
24-
SettingTags []SettingTagModel `json:"settingTags,omitempty"`
13+
Config *ConfigModel `json:"config,omitempty"`
14+
Environment *EnvironmentModel `json:"environment,omitempty"`
15+
ReadOnly bool `json:"readOnly,omitempty"`
16+
Setting *SettingDataModel `json:"setting,omitempty"`
17+
LastUpdaterUserEmail string `json:"lastUpdaterUserEmail,omitempty"`
18+
LastUpdaterUserFullName string `json:"lastUpdaterUserFullName,omitempty"`
19+
IntegrationLinks []IntegrationLinkModel `json:"integrationLinks,omitempty"`
20+
SettingTags []SettingTagModel `json:"settingTags,omitempty"`
2521
// The targeting rule collection.
2622
RolloutRules []RolloutRuleModel `json:"rolloutRules,omitempty"`
2723
// The percentage rule collection.

0 commit comments

Comments
 (0)