[POC] Support to bundle_oauth and bundle_integration_key

[7ail]

Description

Install App

In order to utilise the external OAuth Client created here, changes need to be made in ZAM.

The flow we are striving to achieve is as follows

CHANGES TO ZAS

Since we are dependent on an OAuthClient generated outside of ZAM, changes need to be made to the app manifest.json file to enable the app to make use of it. The plan is to create two new custom hidden fields like the following

"parameters": [
  {
    "name": "bundle_token",
    "type": "bundle_oauth"
  },
  {
    "name": "bundle_integration_key",
    "type": "bundle_integration_key"
  }
]

Features

• Both must exist together
• Both fields are hidden
• bundle_oauth
  ** This field will store the connection_uuid like the pre-existing oauth type
• bundle_integration_key
  ** This field will store the integration key which is specified during the ZIS-Bundle upload (removing the need to rely on procedurally generated versions from ZAM)

For the most part, changes to this flow will remain the unchanged:

We will still query Zendesk App Market for the installation details and check if it is a ZIS App (here). Logic to identify if it utilizes ZIS-Connections needs to be altered to cater for the new connection_uuid and integration_key fields.

If those fields exist, we can go ahead and create the ZIS-Connections url without stitching up the integration key (i.e. app_market_XXX)

DONE WHEN

• ZAS is able to validate both bundle_oauth and bundle_integration_key
• Translations are ignored in this POC

[yoshdog]

It should be noted that although we are proposing this for our new Shopify integration on ZIS, it will ideally be the approach we would use for integrations built on ZIS that require an OAuth + Sidebar app.