@daytona-io/backstage-plugin-daytona
v0.2.7
Published
Welcome to the daytona plugin!
Downloads
2
Maintainers
Readme
daytona
Welcome to the daytona plugin!
This plugin was created through the Backstage CLI
Description
The Daytona plugin provides frontend components to connect to the Daytona API backend and view the workspaces for the authenticated user. You can create new Daytona workspaces directly from Backstage.
Features
- Authenticate the user with Daytona Keycloak
- List all the workspaces for the authenticated user
- List workspaces of a specific repository for the authenticated user with appropriate annotations
- Create a new workspace by navigating to the Daytona instance
Installation
The package shall be installed in the Backstage root directory as below.
yarn --cwd packages/app add @daytona-io/backstage-plugin-daytona
Setup
Standalone App requirements
Install the plugin dependency in your Backstage app package:
# From your Backstage root directory yarn add --cwd packages/app @daytona-io/backstage-plugin-daytona
Add to the app
EntityPage
component. Make sure to addDaytonaOverviewComponent
right afterEntityAboutCard
underoverviewContent
. This will get the repository URL automatically from the entity location metadata to create the Daytona workspaces. Along with that, it will also list all the workspaces, specific to the repository.import { DaytonaOverviewContent } from '@daytona-io/backstage-plugin-daytona'; // Add the DaytonaOverviewContent to show the workspaces for that entity const overviewContent = ( <Grid container spacing={3} alignItems="stretch"> <Grid item md={6}> <EntityAboutCard variant="gridItem" /> </Grid> <Grid item md={6}> <DaytonaOverviewContent /> </Grid> {/* other grid items here*/} </Grid> );
Annotate your component with a valid Git repository if you wish to override the automatically configured repository URL for creating Daytona workspaces.
The annotation key is
daytona.io/repo-url
.Example:
apiVersion: backstage.io/v1alpha1 kind: Component metadata: name: backstage description: backstage.io annotations: daytona.io/repo-url: https://github.com/daytonaio-templates/go spec: type: website lifecycle: production owner: user:guest
App Menu requirements
Ensure that the package is installed as mentioned in the Installation section.
Add to the app
App.tsx
component:// In packages/app/src/App.tsx import { DaytonaPage } from '@daytona-io/backstage-plugin-daytona'; // Add the route to the App path routes const routes = ( <FlatRoutes> {/* other routes here */} <Route path="/daytona" element={<DaytonaPage />} /> </FlatRoutes> );
Add to the app
Root.tsx
component:// In packages/app/src/components/Root/App.tsx import { DaytonaIcon } from '@daytona-io/backstage-plugin-daytona'; // Add the menu to the Root menu sidebar export const Root = ({ children }: PropsWithChildren<{}>) => ( <SidebarPage> <Sidebar> {/* other sidebar items here */} {/* add inside "Menu" SidebarGroup */} <SidebarItem icon={DaytonaIcon} to="daytona" text="Daytona" /> {/* other sidebar items here */} </Sidebar> {children} </SidebarPage> );
Configuration
This plugin requires the domain URL for your Daytona instance. This can be configured in app-config.yaml
file as per below snippet.
daytona:
domain: daytona.domain.com
CORS Configuration for connecting Daytona APIs with Backstage
Below configurations need to be added in the 'watkins' ingress YAML which allows CORS connectivity. It allows Daytona URL along with Backstage URL for CORS policy.
nginx.ingress.kubernetes.io/cors-allow-credentials: "true"
nginx.ingress.kubernetes.io/cors-allow-headers: Authorization, Access-Control-Allow-Origin, Access-Control-Allow-Headers, Origin, Content-Type, Accept, X-Requested-With
nginx.ingress.kubernetes.io/cors-allow-methods: PUT, GET, POST, OPTIONS, DELETE
nginx.ingress.kubernetes.io/cors-allow-origin: https://<backstage-app-url>, https://<daytona-domain-url>
nginx.ingress.kubernetes.io/enable-cors: "true"
Setup Backstage Auth with Keycloak
Backstage shall be registered as a Keycloak client in the default realm. Once the client is created, client ID and secret can be configured in the Backstage instance.
Create Keycloak client in the
default
realm usingbackstage.json
file.Register the newly created client for authentication in backstage.
auth: environment: production providers: daytona: production: clientId: <daytona-client-id> clientSecret: <daytona-client-secret> metadataUrl: https://id.<daytona-domain-url>/realms/default/.well-known/openid-configuration prompt: auto