Designer 10.15 | Cloudstreams Development Help | CloudStreams Provider Project | Updating a Connector by importing a new Swagger or OpenAPI specification file (REST only)
 
Updating a Connector by importing a new Swagger or OpenAPI specification file (REST only)
You can update an existing connector, which was created by using the Swagger or OpenAPI specification file option, by importing a new Swagger or OpenAPI specification file.
To update a connector,
1. In Software AG Designer, click Window > Perspective > Open Perspective > Other > CloudStreams Development to open the CloudStreams Development perspective.
2. Right-click on the connector and select Refactor > Overwrite.
3. In the Refactor dialog box, provide the following details:
*Version: Select 2.0 or 3.0 to import a Swagger or OpenAPI specification file respectively.
*File/URL: Select the file/URL for the Swagger or OpenAPI specification file by clicking Browse.
Note: 
*The imported Swagger or OpenAPI specification file will be processed in the background to provide a high level summary of changes to the connector.
*By importing the new Swagger or OpenAPI specification file, the existing connector will be overwritten with the new connector.
4. Click Next. In the dialog box that appears, you will now see all the newly added resource(s), modified resource(s), removed resource(s), and skipped resource(s). Skipped resources indicate REST resources that are skipped during the parsing of an OpenAPI specification file. These resources might have constructs such as links, callbacks, urlencoded data, which are currently not supported by CloudStreams. The reason why a particular resource is skipped appears when you hover the pointer over the resource. In addition, you will also see the new endpoint URL to which the external REST service is deployed, if updated.
5. Click Apply Changes to update the connector. With this, you have successfully updated the selected connector for the Provider project.
Important: 
The existing resources will be impacted by this update action. The developer is responsible for refreshing the associated Cloud Connector Services.