List Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config

List Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config

list objects of kind DatabaseConfig

Request
URI
GET
https://{api_host}/apis/databases.dataservices.vmware.com/v1alpha1/namespaces/{namespace}/databaseconfigs
COPY
Path Parameters
string
namespace
Required

object name and auth scope, such as for teams and projects

Query Parameters
string
pretty
Optional

If 'true', then the output is pretty printed.

boolean
allowWatchBookmarks
Optional

allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.

string
continue
Optional

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

string
fieldSelector
Optional

A selector to restrict the list of returned objects by their fields. Defaults to everything.

string
labelSelector
Optional

A selector to restrict the list of returned objects by their labels. Defaults to everything.

integer
limit
Optional

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

string
resourceVersion
Optional

resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset

string
resourceVersionMatch
Optional

resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset

boolean
sendInitialEvents
Optional

sendInitialEvents=true may be set together with watch=true. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with "k8s.io/initial-events-end": "true" annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.

When sendInitialEvents option is set, we require resourceVersionMatch option to also be set. The semantic of the watch request is as following: - resourceVersionMatch = NotOlderThan is interpreted as "data at least as new as the provided resourceVersion" and the bookmark event is send when the state is synced to a resourceVersion at least as fresh as the one provided by the ListOptions. If resourceVersion is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed.

  • resourceVersionMatch set to any other value or unset Invalid error is returned.

Defaults to true if resourceVersion="" or resourceVersion="0" (for backward compatibility reasons) and to false otherwise.

integer
timeoutSeconds
Optional

Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.

boolean
watch
Optional

Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.


Authentication
This operation uses the following authentication methods.
Responses
200

OK

{
    "apiVersion": "string",
    "items": [
        {
            "apiVersion": "string",
            "kind": "string",
            "metadata": {
                "creationTimestamp": "string",
                "deletionGracePeriodSeconds": 0,
                "deletionTimestamp": "string",
                "finalizers": [
                    "string"
                ],
                "generateName": "string",
                "generation": 0,
                "managedFields": [
                    {
                        "apiVersion": "string",
                        "fieldsType": "string",
                        "manager": "string",
                        "operation": "string",
                        "subresource": "string",
                        "time": "string"
                    }
                ],
                "name": "string",
                "namespace": "string",
                "ownerReferences": [
                    {
                        "apiVersion": "string",
                        "blockOwnerDeletion": false,
                        "controller": false,
                        "kind": "string",
                        "name": "string",
                        "uid": "string"
                    }
                ],
                "resourceVersion": "string",
                "selfLink": "string",
                "uid": "string"
            },
            "spec": {},
            "status": {
                "conditions": [
                    {
                        "lastTransitionTime": "string",
                        "message": "string",
                        "observedGeneration": 0,
                        "reason": "string",
                        "status": "string",
                        "type": "string"
                    }
                ]
            }
        }
    ],
    "kind": "string",
    "metadata": {
        "continue": "string",
        "remainingItemCount": 0,
        "resourceVersion": "string",
        "selfLink": "string"
    }
}

401

Unauthorized

Operation doesn't return any data structure

Databases Operations
POST
Create Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config
POST
Create Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster
POST
Create Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster
DELETE
Delete Databases Dataservices Vmware Com V 1alpha1 Collection Namespaced Database Config
DELETE
Delete Databases Dataservices Vmware Com V 1alpha1 Collection Namespaced My SQL Cluster
DELETE
Delete Databases Dataservices Vmware Com V 1alpha1 Collection Namespaced Postgres Cluster
DELETE
Delete Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config
DELETE
Delete Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster
DELETE
Delete Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster
GET
List Databases Dataservices Vmware Com V 1alpha1 Database Config For All Namespaces
GET
List Databases Dataservices Vmware Com V 1alpha1 My SQL Cluster For All Namespaces
GET
List Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config
GET
List Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster
GET
List Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster
GET
List Databases Dataservices Vmware Com V 1alpha1 Postgres Cluster For All Namespaces
PATCH
Patch Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config
PATCH
Patch Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config Status
PATCH
Patch Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster
PATCH
Patch Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster Status
PATCH
Patch Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster
PATCH
Patch Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster Status
GET
Read Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config
GET
Read Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config Status
GET
Read Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster
GET
Read Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster Status
GET
Read Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster
GET
Read Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster Status
PUT
Replace Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config
PUT
Replace Databases Dataservices Vmware Com V 1alpha1 Namespaced Database Config Status
PUT
Replace Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster
PUT
Replace Databases Dataservices Vmware Com V 1alpha1 Namespaced My SQL Cluster Status
PUT
Replace Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster
PUT
Replace Databases Dataservices Vmware Com V 1alpha1 Namespaced Postgres Cluster Status