| Templates used: | |
| Release checklists: |
Note: This is required for launch. Only brand new destinations should need to complete all the steps listed here.
Every new destination added to Stitch has a corresponding destination form property for the Connect API.
Step 1: Save a copy of the destination form property template
- Locate the template for the destination:
_templates/connect/destination-form-property.md -
Save a copy into this folder:
_developer-files/connect/api/objects/form-properties/destinationsThe file name should follow this convention:
[destination-name]-object.md.For example:
Amazon Redshiftwould have a file namedamazon-redshift-object.md.
Step 2: Find/replace
-
In the copy of the template, do a case-sensitive find/replace on
DESTINATION-NAME, replacing it with the display name of the destination. The display name is how the provider spells/displays their name.For example: If the name of the destination is
Amazon RedshiftorSnowflake, you would find/replaceDESTINATION-NAMEwithAmazon RedshiftorSnowflake. -
Next, perform a case-sensitive find/replace on
destination-name, replacing it with the key name of the destination. It cannot contain anything but alphanumerical characters and dashes (-).For example: If the display name of the destination is
Amazon RedshiftorSnowflake, you would find/replacedestination-namewithamazon-redshiftandsnowflake.
Step 3: Fill out the template
Fill out the template, using the Destination form property template reference as a guide.
Step 4: Refer to your release checklist
If you’re working on a release, refer to the release checklist you’re using to wrap up the remaining steps for launch:
Back to top
Last updated: 28 July 2021