Connect on Forge with different environments

Hi @jhazelwood ,

I have retried it again and confirmed that I changed the key and redeployed, so I did:

  1. Uninstall all versions of my app from my site
  2. Deployed to development
  3. Changed the Connect key
  4. Deployed to custom environment “my-name”
  5. Installed to Development
  6. Installed to custom environment “my-name”

→ Last step has thrown the 500. I tried this right now, so between 10:45 - 11:00 CET on an app with the id dce24c3d-6542-4a41-a27d-2d06b5001edb.

Regarding the Connect backend: That actually does not exist. We only use confluenceContentProperties from Connect because they do not exist in Forge. This is a Connect property that does not use a real backend. We based this upon this post Using Connect modules in a new Forge app.

Thanks for your assistance.

Best
Johannes