Skip to content

Rayfin up throws a 500 error when SQL databases are not supported in the Workspace #56

Description

What happened?

If a Fabric Apps template is used where a SQL Database should be deployed (or the settings are set in the rayfin config) while workspace-level private links are available, a 500 internal server error is thrown while deploying the app.

See the documentation

Tenant-level private links are available for SQL database, but currently, workspace-level private links are not available in SQL database.

Workaround: Try to use localStorage where data is kept on the server. This is kept outside EntraID so not great for sensitive data!

Steps to reproduce

  1. Create a separate SQL database in your Fabric workspace
  2. If you get this error, Fabric Apps cannot make use of a SQL Database:
Image
  1. Generate a Rayfin app using a template that wants to roll out a SQL database
  2. 'up' the Rayfin app
  3. A generic 500 error occurs in your command prompt
Image

Environment

  • Generic issue

Logs or screenshots

See steps to reproduce.

The roll-out should be able to handle this situation, preventing the 500. Having SQL databases supporting these private endpoints would be great!

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingissue-mappedIssue is mapped to internal trackertriaged

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions