Documentation
¶
Overview ¶
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Service Manager * * API version: 1.0 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
ATTENTION MANUAL CHANGES FOR "Errors" parameter - for details see NGPBUG-371222
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Service Manager *
Service Manager provides REST APIs that are responsible for the creation and consumption of service instances in any connected runtime environment. Use the Service Manager APIs to perform various operations related to your platforms, service brokers, service instances, and service bindings. Get service plans and service offerings associated with your environment. #### Platforms Platforms are OSBAPI-enabled software systems on which applications and services are hosted. With the Service Manager, you can now register your platform and enable it to consume the SAP BTP services from your native environment. This registration results in a returned set of credentials that are needed to deploy the Service Manager agent. #### Service Brokers Service brokers act as brokers between the Service Manager and a platform’s marketplace to advertise catalogues of service offerings and service plans. They also receive and process the requests from the marketplace to provision, bind, unbind, and deprovision these offerings and plans. #### Service Instances Service instances are instantiations of service plans that make the functionality of those service plans available for consumption. #### Service Bindings Service bindings provide access details to existing service instances. The access details are part of the service bindings' ‘credentials’ property, and typically include access URLs and credentials. #### Service Plans Service plans represent sets of capabilities provided by a service offering. For example, database service offerings provide different plans for different database versions or sizes, while the Service Manager plans offer different data access levels. #### Service Offerings Service offerings are advertisements of the services that are supported by a service broker. For example, software that you can consume in the subaccount. Service offerings are related to one or more service plans. *
API version: 1.0
Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Index ¶
- Constants
- type APIResponse
- type AgentVersionsResponseObject
- type CreateByOfferingAndPlanName
- type CreateByPlanId
- type CreateServiceBindingRequestPayload
- type CreatedServiceBindingResponseObject
- type CreatedServiceInstanceResponseObject
- type Credentials
- type CredentialsBasic
- type ErrorBrokerError
- type Label
- type ListedPlatformResponseObject
- type ListedServiceBindingResponseObject
- type ListedServiceBrokerResponseObject
- type ListedServiceInstanceResponseObject
- type ModelError
- type OperationResponseObject
- type PlatformResponseList
- type PlatformResponseObject
- type RegisterPlatformRequestPayload
- type RegisteredPlatformResponseObject
- type ServiceBindingResponseList
- type ServiceBindingResponseObject
- type ServiceBrokerResponseList
- type ServiceBrokerResponseObject
- type ServiceInstanceListResponseObject
- type ServiceInstanceParametersData
- type ServiceInstanceParametersPlain
- type ServiceInstanceResponseList
- type ServiceInstanceResponseObject
- type ServiceManagerLabels
- type ServiceOfferingMetadata
- type ServiceOfferingResponseList
- type ServiceOfferingResponseObject
- type ServicePlanMetadata
- type ServicePlanResponseList
- type ServicePlanResponseObject
- type TransitiveResource
- type UpdatePlatformRequestPayload
- type UpdateServiceInstanceRequestPayload
- type UpdatedPlatformResponseObject
- type UpdatedServiceInstanceResponseObject
Constants ¶
const ( TypeCreate string = "CREATE" TypeUpdate string = "UPDATE" TypeDelete string = "DELETE" )
const ( StateInProgress string = "in progress" StateFailed string = "failed" StateSucceeded string = "succeeded" )
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type APIResponse ¶
type APIResponse struct {
*http.Response `json:"-"`
Message string `json:"message,omitempty"`
// Operation is the name of the swagger operation.
Operation string `json:"operation,omitempty"`
// RequestURL is the request URL. This value is always available, even if the
// embedded *http.Response is nil.
RequestURL string `json:"url,omitempty"`
// Method is the HTTP method used for the request. This value is always
// available, even if the embedded *http.Response is nil.
Method string `json:"method,omitempty"`
// Payload holds the contents of the response body (which may be nil or empty).
// This is provided here as the raw response.Body() reader will have already
// been drained.
Payload []byte `json:"-"`
}
func NewAPIResponse ¶
func NewAPIResponse(r *http.Response) *APIResponse
func NewAPIResponseWithError ¶
func NewAPIResponseWithError(errorMessage string) *APIResponse
type AgentVersionsResponseObject ¶
type AgentVersionsResponseObject struct {
// The list of compatible agent versions for the Cloud Foundry environment.
Cf []string `json:"cf,omitempty"`
// The list of compatible agent versions for the cf-sap environment.
CfSap []string `json:"cf-sap,omitempty"`
// The list of compatible agent versions for the Kubernetes environment.
K8s []string `json:"k8s,omitempty"`
}
type CreateByOfferingAndPlanName ¶
type CreateByOfferingAndPlanName struct {
// The name of the new service instance.<br/> Can't be an empty object.
Name string `json:"name"`
// The name of the service offering to use for the service instance.
ServiceOfferingName string `json:"service_offering_name"`
// The name of the service plan to use for the service instance.
ServicePlanName string `json:"service_plan_name"`
// Some services support providing of additional configuration parameters during instance creation.<br>Pass these parameters as key-value pairs.<br> For the list of supported configuration parameters, see the documentation of a particular service offering.<br> You can also use the *GET /v1/service_instances/{serviceInstanceID}/parameters* API later to view the parameters defined during this step.
Parameters map[string]string `json:"parameters,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type CreateByPlanId ¶
type CreateByPlanId struct {
// The name of the new service instance.<br/> Can't be an empty object.
Name string `json:"name"`
// The ID of the service plan to use for the service instance.
ServicePlanId string `json:"service_plan_id"`
// Some services support providing of additional configuration parameters during instance creation.<br>Pass these parameters as key-value pairs.<br> For the list of supported configuration parameters, see the documentation of a particular service offering.<br> You can also use the *GET /v1/service_instances/{serviceInstanceID}/parameters* API later to view the parameters defined during this step.
Parameters map[string]string `json:"parameters,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type CreateServiceBindingRequestPayload ¶
type CreateServiceBindingRequestPayload struct {
// The name of the service binding.
Name string `json:"name"`
// The id of the service instance associated with the binding.
ServiceInstanceId string `json:"service_instance_id"`
// Some services support providing of additional configuration parameters during binding creation. Pass these parameters as key-value pairs.<br> For the list of supported configuration parameters, see the documentation of a particular service offering.<br>You can also use the *GET /v1/service_bindings/{serviceBindingID}/parameters* API later to view the parameters defined during this step.
Parameters map[string]string `json:"parameters,omitempty"`
// The bind_resource object contains platform-specific information related to the context in which the service is used.<br> The examples of some common fields to use: <br> app_guid - A string GUID of an application associated with the binding. For credentials bindings. Must be unique within the scope of the platform.<br>app_guid - Represents the scope to which the binding applies within the platform. <br>For example, in Kubernetes it can map to a namespace.<br> The scope of what the platform maps the app_guid to is platform-specific and can vary across binding requests.<br>route - URL of the intermediate application. For route services bindings.
BindResource *interface{} `json:"bind_resource,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type CreatedServiceBindingResponseObject ¶
type CreatedServiceBindingResponseObject struct {
// The ID of the service binding.
Id string `json:"id,omitempty"`
// Whether the resource is ready to be used.
Ready bool `json:"ready,omitempty"`
// The name of the service binding.
Name string `json:"name,omitempty"`
// The ID of the service instance associated with the binding.
ServiceInstanceId string `json:"service_instance_id,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// Credentials to access the binding.
Credentials *interface{} `json:"credentials,omitempty"`
// The bound resources.
BindResource map[string]string `json:"bind_resource,omitempty"`
// The time the binding was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the binding was updated.<br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type CreatedServiceInstanceResponseObject ¶
type CreatedServiceInstanceResponseObject struct {
// The ID of the service instance.
Id string `json:"id,omitempty"`
// Whether the service instance is ready for consumption.
Ready bool `json:"ready,omitempty"`
// The name of the service instance.
Name string `json:"name,omitempty"`
// The ID of the serivce plan associated with the service instance.
ServicePlanId string `json:"service_plan_id,omitempty"`
// The ID of the platform associated with the service instance.
PlatformId string `json:"platform_id,omitempty"`
// The URL of the web-based management UI for the service instance.
DashboardUrl string `json:"dashboard_url,omitempty"`
// The ID of the instance to which the service instance refers.
ReferencedInstanceId string `json:"referenced_instance_id,omitempty"`
Shared bool `json:"shared,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// The maintenance info associated with the service instance.
MaintenanceInfo map[string]string `json:"maintenance_info,omitempty"`
// Whether the resource can be used.
Usable bool `json:"usable,omitempty"`
// The time the service instance was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service instance was updated.<br/>In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type Credentials ¶
type Credentials struct {
Basic *CredentialsBasic `json:"basic,omitempty"`
}
Credentials to authenticate with the SAP Service Manager.
type CredentialsBasic ¶
type ErrorBrokerError ¶
type ErrorBrokerError struct {
// The broker status code.
StatusCode int32 `json:"statusCode,omitempty"`
// A machine-readable error string that may be returned by the broker.
ErrorMessage string `json:"errorMessage,omitempty"`
// A human-readable description of the error that may be returned by the broker.
Description string `json:"description,omitempty"`
// ResponseError is set to the error that occurred when unmarshalling a response body from the broker.
ResponseError string `json:"responseError,omitempty"`
}
The broker error
type Label ¶
type Label struct {
// The operation to perform on a label.<br/><br/> Possible values:
Op string `json:"op,omitempty"`
// The name of the label.
Key string `json:"key,omitempty"`
// The list of values for the label
Values []string `json:"values,omitempty"`
}
The request object that contains details about the labels to update.
type ListedPlatformResponseObject ¶
type ListedPlatformResponseObject struct {
// The ID of the platform.</br> You can use this ID to get details about the platform, to update or to delete it.<br/> See the GET, PATCH, or DELETE APIs for the Platforms group.
Id string `json:"id,omitempty"`
// Whether the platform is ready for consumption.
Ready bool `json:"ready,omitempty"`
// The type of the platform.<br><br> Possible values:
Type_ string `json:"type,omitempty"`
// The name of the platform.
Name string `json:"name,omitempty"`
// The description of the platform.
Description string `json:"description,omitempty"`
// The time the platform was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the platform was updated. <br/>In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type ListedServiceBindingResponseObject ¶
type ListedServiceBindingResponseObject struct {
// The ID of the service binding.
Id string `json:"id,omitempty"`
// Whether the service binding is ready.
Ready bool `json:"ready,omitempty"`
// The name of the service binding.
Name string `json:"name,omitempty"`
// The ID of the service instance associated with the binding.
ServiceInstanceId string `json:"service_instance_id,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// Contains the resources associated with the binding.
BindResource map[string]string `json:"bind_resource,omitempty"`
// Credentials to access the binding.
Credentials *interface{} `json:"credentials,omitempty"`
// The time the binding was created.<br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the binding was updated.<br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type ListedServiceBrokerResponseObject ¶
type ListedServiceBrokerResponseObject struct {
// The ID of the service broker.
Id string `json:"id"`
// Whether the service broker is ready.
Ready bool `json:"ready,omitempty"`
// The name of the service broker.
Name string `json:"name"`
// The description of the service broker.
Description string `json:"description,omitempty"`
// The URL of the service broker.
BrokerUrl string `json:"broker_url,omitempty"`
// The time the service broker was created. <br/><br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service broker was updated. <br/>In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type ListedServiceInstanceResponseObject ¶
type ListedServiceInstanceResponseObject struct {
// The ID of the service instance.
Id string `json:"id,omitempty"`
// Whether the service instance is ready.
Ready bool `json:"ready,omitempty"`
// The name of the service instance.
Name string `json:"name,omitempty"`
// The ID of the service plan associated with the service instance.
ServicePlanId string `json:"service_plan_id,omitempty"`
// The ID of the platform to which the service instance belongs.
PlatformId string `json:"platform_id,omitempty"`
// The URL of the web-based management UI for the service instance.
DashboardUrl string `json:"dashboard_url,omitempty"`
// The ID of the instance to which the service instance refers.
ReferencedInstanceId string `json:"referenced_instance_id,omitempty"`
Shared bool `json:"shared,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// The maintenance information associated with the service instance.
MaintenanceInfo map[string]string `json:"maintenance_info,omitempty"`
// Whether the service instance can be used.
Usable bool `json:"usable,omitempty"`
// The time the service instance was created.<br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service instance was updated.<br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type ModelError ¶
type ModelError struct {
// The name of the error.
Error_ string `json:"error,omitempty"`
// The description of the error.
Description string `json:"description,omitempty"`
BrokerError *ErrorBrokerError `json:"brokerError,omitempty"`
}
A response object that contains details about the error.
type OperationResponseObject ¶
type OperationResponseObject struct {
// The ID of the operation.
Id string `json:"id,omitempty"`
// Whether the resource is ready.
Ready bool `json:"ready,omitempty"`
// The type of the operation.<br><br> Possible values:
Type_ string `json:"type,omitempty"`
// Valid values are: in progress, succeeded, and failed. <br> While the state is \"in progress\", the platform should continue polling. <br/> The responses: \"state\": \"succeeded\" or \"state\": \"failed\" must cause the platform to stop polling.
State string `json:"state,omitempty"`
// Details about the operation for customer-facing UI.
Description string `json:"description,omitempty"`
// The ID of the resource. <br> Exists if: \"state\": \"succeeded\", and also for PATCH and DELETE requests
ResourceId string `json:"resource_id,omitempty"`
TransitiveResources []TransitiveResource `json:"transitive_resources,omitempty"`
// The type of the resource (e.g. service_brokers, service_instances).
ResourceType string `json:"resource_type,omitempty"`
// The ID of the platform associated with the operation.
PlatformId string `json:"platform_id,omitempty"`
// The correlation ID received from the request related to this operation.
CorrelationId string `json:"correlation_id,omitempty"`
// Whether the operation has reached a checkpoint and can be executed again.
Reschedule bool `json:"reschedule,omitempty"`
// The time the resource is scheduled for deletion. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
DeletionScheduled time.Time `json:"deletion_scheduled,omitempty"`
// The time the resource was created. <br/>In ISO 8601 format.
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the resource was updated. <br/>In ISO 8601 format. <br/>Recommended field if \"state\": \"succeeded\" or \"state\": \"failed\".
UpdatedAt time.Time `json:"updated_at,omitempty"`
// The list of the errors if the operation has failed.
// Manually changed from type []ModelError to generic json.RawMessage due to NGPBUG-371222
Errors json.RawMessage `json:"errors,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type PlatformResponseList ¶
type PlatformResponseList struct {
// Use this token when you call the API again to get more platforms associated with your subaccount.</br> The token field indicates that the total number of platforms to view in the list (num_items) is larger than the defined maximum number of platforms to be returned after a single API call (max_items). </br> If the field is not present, either all the platforms were included in the first response, or you have reached the end of the list.
Token string `json:"token,omitempty"`
// The number of platforms associated with the subaccount.
NumItems int32 `json:"num_items,omitempty"`
// The list of response objects that contains details about the platforms.
Items []ListedPlatformResponseObject `json:"items,omitempty"`
}
type PlatformResponseObject ¶
type PlatformResponseObject struct {
// The ID of the platform. <br/> You can use this ID to update or to delete the platform.<br/> See the PATCH and DELETE calls for the **Platforms** group.
Id string `json:"id,omitempty"`
// Whether the platform is ready for consumption.
Ready bool `json:"ready,omitempty"`
LastOperation *OperationResponseObject `json:"last_operation,omitempty"`
// The type of the platform.<br><br> Possible values:
Type_ string `json:"type,omitempty"`
// The name of the platform.
Name string `json:"name,omitempty"`
// The description of the platform.
Description string `json:"description,omitempty"`
// The time the platform was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the platform was updated. <br/>In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels ServiceManagerLabels `json:"labels,omitempty"`
}
type RegisterPlatformRequestPayload ¶
type RegisterPlatformRequestPayload struct {
// The CLI-friendly name of the platform.<br/>A CLI-friendly name is a short string that only contains alphanumeric characters, periods, and hyphens.<br> It can't contain white spaces. <br>The name must not exceed 255 characters, but it is recommended to keep it much shorter, for the convenience of using short names in CLI commands.
Name string `json:"name"`
// The type of the platform. <br><br> Possible values:
Type_ string `json:"type"`
// The description of the platform for customer-facing UIs.
Description string `json:"description,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type RegisteredPlatformResponseObject ¶
type RegisteredPlatformResponseObject struct {
// The ID of the platform.<br>You can use this ID to get details about the platform, to update, or to delete the platform.<br/> See the GET, PATCH, and DELETE APIs for the **Platforms** group.
Id string `json:"id,omitempty"`
// Whether the platform is ready for consumption.
Ready bool `json:"ready,omitempty"`
// The type of the platform.<br/><br/> Possible values:
Type_ string `json:"type,omitempty"`
// The technical name of the platform.
Name string `json:"name,omitempty"`
// The description of the platform.
Description string `json:"description,omitempty"`
Credentials *Credentials `json:"credentials,omitempty"`
// The time the platform was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the platform was updated. <br/>In ISO 8601 format. </br>
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type ServiceBindingResponseList ¶
type ServiceBindingResponseList struct {
// Use this token when you call the API again to get more service bindings associated with your subaccount.</br> The token field indicates that the total number of service bindings to view in the list (num_items) is larger than the defined maximum number of service bindings to be returned after a single API call (max_items). </br> If the field is not present, either all the service bindings were included in the first response, or you have reached the end of the list.
Token string `json:"token,omitempty"`
// The number of the service bindings associated with the subaccount.
NumItems int32 `json:"num_items,omitempty"`
// The list of the response objects that contains details about the service bindings.
Items []ListedServiceBindingResponseObject `json:"items,omitempty"`
}
type ServiceBindingResponseObject ¶
type ServiceBindingResponseObject struct {
// The ID of the service binding.
Id string `json:"id,omitempty"`
// Whether the service binding is ready.
Ready bool `json:"ready,omitempty"`
LastOperation *OperationResponseObject `json:"last_operation,omitempty"`
// The name of the service binding.
Name string `json:"name,omitempty"`
// The ID of the service instance associated with the binding.
ServiceInstanceId string `json:"service_instance_id,omitempty"`
// The ID of the subaccount.
SubaccountId string `json:"subaccount_id,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// Credentials to access the binding.
Credentials json.RawMessage `json:"credentials,omitempty"`
// The bound resources.
BindResource map[string]string `json:"bind_resource,omitempty"`
// The time the binding was created.<br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the binding was updated.<br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels ServiceManagerLabels `json:"labels,omitempty"`
}
type ServiceBrokerResponseList ¶
type ServiceBrokerResponseList struct {
// Use this token when you call the API again to get more service brokers associated with your subaccount.</br> The token field indicates that the total number of service brokers to view in the list (num_items) is larger than the defined maximum number of service brokers to be returned after a single API call (max_items). </br> If the field is not present, either all the service brokers were included in the first response, or you have reached the end of the list.
Token string `json:"token,omitempty"`
// The number of the service brokers associated with the subaccount.
NumItems int32 `json:"num_items,omitempty"`
// The list of response objects that contains details about the service brokers.
Items []ListedServiceBrokerResponseObject `json:"items,omitempty"`
}
type ServiceBrokerResponseObject ¶
type ServiceBrokerResponseObject struct {
// The ID of the service broker.
Id string `json:"id"`
// Whether the service broker is ready.
Ready bool `json:"ready,omitempty"`
LastOperation *OperationResponseObject `json:"last_operation,omitempty"`
// The name of the service broker.
Name string `json:"name"`
// The description of the service broker.
Description string `json:"description,omitempty"`
// The URL of the service broker.
BrokerUrl string `json:"broker_url,omitempty"`
// The time the service broker was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service broker was updated. <br/>In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels ServiceManagerLabels `json:"labels,omitempty"`
}
type ServiceInstanceListResponseObject ¶
type ServiceInstanceListResponseObject struct {
// The ID of the service instance.
Id string `json:"id,omitempty"`
Ready bool `json:"ready,omitempty"`
//LastOperation *OperationResponseObject `json:"last_operation,omitempty"`
// The name of the service instance.
Name string `json:"name,omitempty"`
// The ID of the serivce plan.
ServicePlanId string `json:"service_plan_id,omitempty"`
// The platform ID.
PlatformId string `json:"platform_id,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// Wheher the resource can be used.
Usable bool `json:"usable,omitempty"`
// The id of the subaccount
SubaccountId string `json:"subaccount_id"`
// The time the resource was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the resource was updated. <br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels ServiceManagerLabels `json:"labels,omitempty"`
}
type ServiceInstanceParametersData ¶
type ServiceInstanceParametersData struct {
Parameters map[string]interface{} `json:"data,omitempty"`
}
type ServiceInstanceParametersPlain ¶
type ServiceInstanceParametersPlain struct {
Parameters map[string]interface{} `json:"-"`
}
type ServiceInstanceResponseList ¶
type ServiceInstanceResponseList struct {
// Use this token when you call the API again to get more service instances associated with your subaccount.</br> The token field indicates that the total number of service instances to view in the list (num_items) is larger than the defined maximum number of service instances to be returned after a single API call (max_items). </br> If the field is not present, either all the instances were included in the first response, or you have reached the end of the list.
Token string `json:"token,omitempty"`
// The number of service instances associated with the subaccount.
NumItems int32 `json:"num_items,omitempty"`
// The list of response objects that contains details about the service instances.
Items []ListedServiceInstanceResponseObject `json:"items,omitempty"`
}
type ServiceInstanceResponseObject ¶
type ServiceInstanceResponseObject struct {
// The ID of the service instance.
Id string `json:"id,omitempty"`
Ready bool `json:"ready,omitempty"`
LastOperation *OperationResponseObject `json:"last_operation,omitempty"`
// The name of the service instance.
Name string `json:"name,omitempty"`
// The ID of the serivce plan.
ServicePlanId string `json:"service_plan_id,omitempty"`
// The ID of the subaccount.
SubaccountId string `json:"subaccount_id,omitempty"`
// The platform ID.
PlatformId string `json:"platform_id,omitempty"`
// The URL of a web-based management user interface for the service instance, also known as service dashboard.
DashboardUrl string `json:"dashboard_url,omitempty"`
// The ID of the instance to which the service instance refers.
ReferencedInstanceId string `json:"referenced_instance_id,omitempty"`
Shared bool `json:"shared,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// The maintenance info for the resource.
MaintenanceInfo map[string]string `json:"maintenance_info,omitempty"`
// Wheher the resource can be used.
Usable bool `json:"usable,omitempty"`
// The time the resource was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the resource was updated. <br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels ServiceManagerLabels `json:"labels,omitempty"`
//MANUALLY ADDED PARAMETER FOR SERVICE INSTANCE CONFIGURATION
Parameters string
}
type ServiceManagerLabels ¶
func (*ServiceManagerLabels) UnmarshalJSON ¶
func (s *ServiceManagerLabels) UnmarshalJSON(data []byte) error
type ServiceOfferingMetadata ¶
type ServiceOfferingMetadata struct {
// The description of the service offering.
LongDescription string `json:"longDescription,omitempty"`
// The URL to the associated documentation.
DocumentationUrl string `json:"documentationUrl,omitempty"`
// The name of the service offering for customer-facing UIs.
DisplayName string `json:"displayName,omitempty"`
// The URL to the associated image.
ImageUrl string `json:"imageUrl,omitempty"`
// The support URL for the service offering.
SupportUrl string `json:"supportUrl,omitempty"`
}
type ServiceOfferingResponseList ¶
type ServiceOfferingResponseList struct {
// Use this token when you call the API again to get more service offerings associated with your subaccount.</br> The token field indicates that the total number of service offerings to view in the list (num_items) is larger than the defined maximum number of service offerings to be returned after a single API call (max_items). </br> If the field is not present, either all the service offerings were included in the first response, or you have reached the end of the list.
Token string `json:"token,omitempty"`
// The number of service offerings associated with the subaccount.
NumItems int32 `json:"num_items,omitempty"`
// The list of the service offerings.
Items []ServiceOfferingResponseObject `json:"items,omitempty"`
}
type ServiceOfferingResponseObject ¶
type ServiceOfferingResponseObject struct {
// The ID of the service offering.
Id string `json:"id,omitempty"`
// Whether the service offering is ready to be advertised.
Ready bool `json:"ready,omitempty"`
// The name of the service offering.
Name string `json:"name,omitempty"`
// The description of the service offering.
Description string `json:"description,omitempty"`
// Whether the service offering is bindable.
Bindable bool `json:"bindable,omitempty"`
// Whether the service instances associated with the service offering can be retrieved.
InstancesRetrievable bool `json:"instances_retrievable,omitempty"`
// Whether the bindings associated with the service offering can be retrieved.
BindingsRetrievable bool `json:"bindings_retrievable,omitempty"`
// Whether the offered plan can be updated.
PlanUpdateable bool `json:"plan_updateable,omitempty"`
// Whether the context for the service offering can be updated.
AllowContextUpdates bool `json:"allow_context_updates,omitempty"`
// The list of tags for the service offering.
Tags []string `json:"tags,omitempty"`
Metadata *ServiceOfferingMetadata `json:"metadata,omitempty"`
// The ID of the broker that provides the service plan.
BrokerId string `json:"broker_id,omitempty"`
// The ID of the service offering as provided by the catalog.
CatalogId string `json:"catalog_id,omitempty"`
// The catalog name of the service offering.
CatalogName string `json:"catalog_name,omitempty"`
// The time the service offering was created. <br> In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service offering was updated. <br/> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
}
type ServicePlanMetadata ¶
type ServicePlanMetadata struct {
// Platforms supported by the service plan.
SupportedPlatforms []string `json:"supportedPlatforms,omitempty"`
// The earliest supported OSB version.
SupportedMinOSBVersion json.Number `json:"supportedMinOSBVersion,omitempty"`
// The latest supported OSB version.
SupportedMaxOSBVersion json.Number `json:"supportedMaxOSBVersion,omitempty"`
// MANUALLY ADDED - DUE TO MISMATCH OF CIS API AND CIS CLI INTERFACE
SupportsInstanceSharing bool `json:"supportsInstanceSharing,omitempty"`
}
type ServicePlanResponseList ¶
type ServicePlanResponseList struct {
// Use this token when you call the API again to get more service plans associated with your subaccount.</br> The token field indicates that the total number of service plans to view in the list (num_items) is larger than the defined maximum number of ervice plans to be returned after a single API call (max_items). </br> If the field is not present, either all the service plans were included in the first response, or you have reached the end of the list.
Token string `json:"token,omitempty"`
// The number of service plans associated with the subaccount.
NumItems int32 `json:"num_items,omitempty"`
// The list of the response objects that contain details about the service plans.
Items []ServicePlanResponseObject `json:"items,omitempty"`
}
type ServicePlanResponseObject ¶
type ServicePlanResponseObject struct {
// The ID of the service plan.
Id string `json:"id,omitempty"`
// Whether the service plan is ready.
Ready bool `json:"ready,omitempty"`
// The name of the service plan.
Name string `json:"name,omitempty"`
// The description of the service plan.
Description string `json:"description,omitempty"`
// The ID of the service plan in the service broker catalog.
CatalogId string `json:"catalog_id,omitempty"`
// The name of the associated service broker catalog.
CatalogName string `json:"catalog_name,omitempty"`
// Whether the service plan is free.
Free bool `json:"free,omitempty"`
// Whether the service plan is bindable.
Bindable bool `json:"bindable,omitempty"`
Metadata *ServicePlanMetadata `json:"metadata,omitempty"`
// The ID of the service offering.
ServiceOfferingId string `json:"service_offering_id,omitempty"`
// The time the service plan was created.<br> In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service plan was updated.<br> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
}
type TransitiveResource ¶
type TransitiveResource struct {
// The ID of the resource.
Id string `json:"id,omitempty"`
// The type of the resource.
Type_ string `json:"type,omitempty"`
// The type of the operation associated with the resource.
OperationType string `json:"operation_type,omitempty"`
// The minimum criteria required to use the resource in the context of the platform.
Criteria string `json:"criteria,omitempty"`
}
type UpdatePlatformRequestPayload ¶
type UpdatePlatformRequestPayload struct {
// The ID of the platform to update. <br>Platform ID is a globally unique identifier (GUID). <br> GUID must be longer than 50 characters and only contains uppercase and lowercase letters, decimal digits, hyphens, periods, and underscores.
Id string `json:"id,omitempty"`
// The CLI-friendly name of the platform to update.<br>A CLI-friendly name is a short string that only contains alphanumeric characters, periods, and hyphens. <br> It can't contain white spaces. <br> The name must not exceed 255 characters, but it is recommended to keep it much shorter, for the convenience of using short names in CLI commands.
Name string `json:"name,omitempty"`
// The type of the platform.<br/><br/> Possible values:
Type_ string `json:"type,omitempty"`
// The description of the platform for customer-facing UIs.
Description string `json:"description,omitempty"`
Labels *[]Label `json:"labels,omitempty"`
}
type UpdateServiceInstanceRequestPayload ¶
type UpdateServiceInstanceRequestPayload struct {
// The name of the service instance to update.
Name string `json:"name,omitempty"`
// The ID of the service plan for the service instance to update.
ServicePlanId string `json:"service_plan_id,omitempty"`
// Some services support providing of additional configuration parameters during instance creation.<br>You can update these parameters.<br>For the list of supported configuration parameters, see the documentation of a particular service offering.<br>You can also use the *GET /v1/service_instances/{serviceInstanceID}/parameters* API later to view the parameters defined during this step.
Parameters map[string]string `json:"parameters,omitempty"`
Labels *[]Label `json:"labels,omitempty"`
}
type UpdatedPlatformResponseObject ¶
type UpdatedPlatformResponseObject struct {
// The ID of the updated platform.<br/>
Id string `json:"id,omitempty"`
// Whether the resource is ready for consumption.
Ready bool `json:"ready,omitempty"`
// The type of the platform.<br><br> Possible values:
Type_ string `json:"type,omitempty"`
// The technical name of the platform.
Name string `json:"name"`
// The description of the platform for customer-facing UIs.
Description string `json:"description,omitempty"`
// The time the platform was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the platform was updated. <br/>In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
type UpdatedServiceInstanceResponseObject ¶
type UpdatedServiceInstanceResponseObject struct {
// The ID of the service instance.
Id string `json:"id,omitempty"`
Ready bool `json:"ready,omitempty"`
// The name of the service instance.
Name string `json:"name,omitempty"`
// The ID of the service plan associated with the service instance.
ServicePlanId string `json:"service_plan_id,omitempty"`
// The ID of the platform associated with the service instance.
PlatformId string `json:"platform_id,omitempty"`
// The URL of the web-based management UI for the service instance.
DashboardUrl string `json:"dashboard_url,omitempty"`
// The ID of the instance to which the service instance refers.
ReferencedInstanceId string `json:"referenced_instance_id,omitempty"`
Shared bool `json:"shared,omitempty"`
// Contextual data for the resource.
Context json.RawMessage `json:"context,omitempty"`
// The maintenance info for the resource.
MaintenanceInfo map[string]string `json:"maintenance_info,omitempty"`
Usable bool `json:"usable,omitempty"`
// The time the service instance was created. <br/>In ISO 8601 format:</br> YYYY-MM-DDThh:mm:ssTZD
CreatedAt time.Time `json:"created_at,omitempty"`
// The last time the service instance was updated. </br> In ISO 8601 format.
UpdatedAt time.Time `json:"updated_at,omitempty"`
Labels *map[string][]string `json:"labels,omitempty"`
}
Source Files
¶
- labels.go
- model_agent_versions_response_object.go
- model_create_by_offering_and_plan_name.go
- model_create_by_plan_id.go
- model_create_service_binding_request_payload.go
- model_created_service_binding_response_object.go
- model_created_service_instance_response_object.go
- model_credentials.go
- model_credentials_basic.go
- model_error.go
- model_error_broker_error.go
- model_label.go
- model_listed_platform_response_object.go
- model_listed_service_binding_response_object.go
- model_listed_service_broker_response_object.go
- model_listed_service_instance_response_object.go
- model_operation_response_object.go
- model_platform_response_list.go
- model_platform_response_object.go
- model_register_platform_request_payload.go
- model_registered_platform_response_object.go
- model_service_binding_response_list.go
- model_service_binding_response_object.go
- model_service_broker_response_list.go
- model_service_broker_response_object.go
- model_service_instance_parameters.go
- model_service_instance_response_list.go
- model_service_instance_response_object.go
- model_service_offering_metadata.go
- model_service_offering_response_list.go
- model_service_offering_response_object.go
- model_service_plan_metadata.go
- model_service_plan_response_list.go
- model_service_plan_response_object.go
- model_transitive_resource.go
- model_update_platform_request_payload.go
- model_update_service_instance_request_payload.go
- model_updated_platform_response_object.go
- model_updated_service_instance_response_object.go
- resource_state.go
- response.go