Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add more to systems page #341

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

adityachoudhari26
Copy link
Contributor

@adityachoudhari26 adityachoudhari26 commented Feb 25, 2025

Summary by CodeRabbit

  • New Features

    • Introduced a “New Release” option (with a rocket icon) in the deployment dropdown for quick release creation.
    • Added enhanced components to display deployment environment details, interactive release information (including job status charts and icons), and an updated system deployments table for easier management.
    • New components for displaying deployment environment and release information, including status icons and lazy-loading for improved performance.
    • Added a new procedure for querying releases based on deployment and environment, enhancing data retrieval capabilities.
  • Refactor / Chores

    • Streamlined file organization and data fetching logic for increased responsiveness.
    • Improved database performance with new indexing optimizations.

Copy link
Contributor

coderabbitai bot commented Feb 25, 2025

Walkthrough

The changes reorganize the project’s component structure and update import paths across several UI files. A previously removed deployment table component is reintroduced under a new path, and new components for deployment handling and release information have been added. Numerous import paths are updated to reflect a revised file structure, and backend logic is simplified by removing legacy queries and adding new procedures. Additionally, database schema changes include the creation of new indexes and a journal entry for tracking schema updates.

Changes

File(s) Change Summary
apps/webservice/src/app/.../systems/SystemDeploymentTable.tsx
apps/webservice/src/app/.../systems/page.tsx
Removed the original SystemDeploymentTable and updated its import reference; reintroduced as a new component in a subdirectory.
ApprovalCheck.tsx
EnvironmentApprovalRow.tsx
ReleaseEnvironmentCell.tsx
TableCells.tsx
DeploymentCTA.tsx
DeploymentPageContent.tsx
.../settings/page.tsx
DeploymentBarChart.tsx
Updated import paths for components (e.g. ApprovalDialog, CreateReleaseDialog, LazyReleaseEnvironmentCell, etc.) to reflect new absolute or simplified directory structures.
DeploymentOptionsDropdown.tsx
TableDeployments.tsx
SystemDeploymentTable.tsx (new location)
Added new deployment components including dropdown options with a “New Release” item and a complete deployment table with sub-components (EnvHeader).
ReleaseInfo.tsx
StatusIcon.tsx
Introduced new components for displaying release details and rendering status icons based on job statuses.
packages/api/src/router/deployment.ts
packages/api/src/router/release-deploy.ts
packages/api/src/router/release.ts
Simplified API logic by removing the latestActiveReleaseSubQuery, adding a logging statement, and introducing a new procedure (byDeploymentAndEnvironment) with authorization checks.
packages/db/drizzle/0072_dapper_sphinx.sql
packages/db/drizzle/meta/_journal.json
packages/db/src/schema/release.ts
Updated database schema by adding a new index on the created_at/createdAt column, and recorded the change in the journal.

Sequence Diagram(s)

sequenceDiagram
  participant U as User
  participant SDT as SystemDeploymentTable Component
  participant API as API Server
  participant DT as DeploymentTable Component
  participant DD as Dropdown (CreateDeployment/DeleteSystem)

  U->>SDT: Scrolls into view
  SDT->>API: Fetch environments & deployments
  API-->>SDT: Return data
  SDT->>DT: Render deployment table
  DT->>DD: Render dropdown options (Create/Delete)
  U->>DD: Interact with dropdown
Loading
sequenceDiagram
  participant U as User
  participant DOD as DeploymentOptionsDropdown
  participant CRD as CreateReleaseDialog

  U->>DOD: Clicks "New Release" (IconRocket)
  DOD-->>CRD: Open release creation dialog (prevent default)
  CRD->>U: Render UI for new release creation
  U->>CRD: Submit release details
Loading

Poem

In a meadow of code so vast and deep,
I hop and skip through changes, taking a leap.
Reorganized paths shine like morning dew,
New components bloom in a vibrant hue.
APIs and indexes now cheerfully rhyme,
A bunny's delight in every commit and line!
🐇🌼 Happy coding, one leap at a time!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments. If you are seeing this consistently, please check "Code review limits" under "Moderation" settings.

Actionable comments posted: 3

🧹 Nitpick comments (9)
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/release-cell/TableCells.tsx (1)

122-265: Consider refactoring the Release component for better maintainability.

The component could benefit from:

  1. Extracting data fetching and transformation logic into a custom hook
  2. Splitting the visualization logic into a separate component
  3. Simplifying the lodash chain operations

Example of extracting data fetching into a custom hook:

const useReleaseJobTriggers = (
  workspaceSlug: string,
  releaseId: string,
  environmentId: string
) => {
  const workspaceId = api.workspace.bySlug.useQuery(workspaceSlug);
  
  const filter: JobCondition = {
    type: FilterType.Comparison,
    operator: ComparisonOperator.And,
    conditions: [
      {
        type: JobFilterType.Release,
        operator: ColumnOperator.Equals,
        value: releaseId,
      },
      {
        type: JobFilterType.Environment,
        operator: ColumnOperator.Equals,
        value: environmentId,
      },
    ],
  };

  const releaseJobTriggersQ = api.job.config.byWorkspaceId.list.useQuery(
    { workspaceId: workspaceId.data?.id ?? "", filter },
    { enabled: isPresent(workspaceId.data?.id) },
  );

  return {
    isLoading: releaseJobTriggersQ.isLoading,
    data: releaseJobTriggersQ.data ?? [],
  };
};
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/StatusIcon.tsx (1)

21-83: Reduce style duplication by extracting common styles.

The styling pattern "rounded-full p-1 dark:text-black" is repeated across all status icons. Consider extracting these common styles to reduce duplication.

Here's how you could refactor this:

+const baseIconStyles = "rounded-full p-1 dark:text-black";
+
 export const StatusIcon: React.FC<{
   statuses: JobStatusType[];
 }> = ({ statuses }) => {
   const inProgress = statuses.some((s) => s === JobStatus.InProgress);
   if (inProgress)
     return (
-      <div className="animate-spin rounded-full bg-blue-400 p-1 dark:text-black">
+      <div className={`${baseIconStyles} animate-spin bg-blue-400`}>
         <IconLoader2 strokeWidth={2} className="h-4 w-4" />
       </div>
     );
   // ... similar changes for other status checks
   return (
-    <div className="rounded-full bg-green-400 p-1 dark:text-black">
+    <div className={`${baseIconStyles} bg-green-400`}>
       <IconCircleCheck strokeWidth={2} className="h-4 w-4" />
     </div>
   );
 };
packages/api/src/router/release.ts (1)

451-494: Consider optimizing the database queries.

The current implementation makes two separate database calls:

  1. First to fetch the release channel
  2. Then to fetch the release

Consider combining these into a single query using joins for better performance.

Here's a suggested optimization:

-        const rc = await ctx.db
-          .select()
-          .from(environment)
-          .innerJoin(
-            environmentPolicy,
-            eq(environment.policyId, environmentPolicy.id),
-          )
-          .innerJoin(
-            environmentPolicyReleaseChannel,
-            eq(environmentPolicyReleaseChannel.policyId, environmentPolicy.id),
-          )
-          .innerJoin(
-            releaseChannel,
-            eq(environmentPolicyReleaseChannel.channelId, releaseChannel.id),
-          )
-          .where(
-            and(
-              eq(environment.id, environmentId),
-              eq(releaseChannel.deploymentId, deploymentId),
-            ),
-          )
-          .then(takeFirstOrNull);
-
-        return ctx.db
+        return ctx.db
           .select()
           .from(release)
+          .leftJoin(
+            db
+              .select()
+              .from(environment)
+              .innerJoin(
+                environmentPolicy,
+                eq(environment.policyId, environmentPolicy.id),
+              )
+              .innerJoin(
+                environmentPolicyReleaseChannel,
+                eq(environmentPolicyReleaseChannel.policyId, environmentPolicy.id),
+              )
+              .innerJoin(
+                releaseChannel,
+                eq(environmentPolicyReleaseChannel.channelId, releaseChannel.id),
+              )
+              .where(
+                and(
+                  eq(environment.id, environmentId),
+                  eq(releaseChannel.deploymentId, deploymentId),
+                ),
+              )
+              .as("rc"),
+            eq(release.deploymentId, deploymentId),
+          )
           .where(
             and(
               eq(release.deploymentId, deploymentId),
-              rc != null
-                ? releaseMatchesCondition(
-                    ctx.db,
-                    rc.release_channel.releaseFilter,
-                  )
-                : undefined,
+              releaseMatchesCondition(
+                ctx.db,
+                sql<any>`rc.release_channel_release_filter`,
+              ),
             ),
           )
           .orderBy(desc(release.createdAt))
           .limit(1)
           .then(takeFirstOrNull);

Additionally, consider adding error handling for cases where the queries fail:

       .query(async ({ ctx, input }) => {
         const { deploymentId, environmentId } = input;
+        try {
           // ... query implementation ...
+        } catch (error) {
+          ctx.logger.error("Failed to fetch release", { error, input });
+          throw new TRPCError({
+            code: "INTERNAL_SERVER_ERROR",
+            message: "Failed to fetch release",
+          });
+        }
       }),
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/system-deployment-table/SystemDeploymentTable.tsx (1)

73-79: Consider adding loading states for better UX.

While the lazy loading implementation is good, the component could benefit from displaying loading states when fetching environments and deployments data.

Add loading states to improve user experience:

       <div ref={ref} className="overflow-hidden rounded-md border">
+        {(environments.isLoading || deployments.isLoading) && (
+          <div className="flex h-32 items-center justify-center">
+            <IconLoader2 className="h-6 w-6 animate-spin text-muted-foreground" />
+          </div>
+        )}
+        {!environments.isLoading && !deployments.isLoading && (
         <DeploymentTable
           workspace={workspace}
           systemSlug={system.slug}
           environments={environments.data ?? []}
           deployments={deployments.data ?? []}
         />
+        )}
       </div>
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/ReleaseInfo.tsx (2)

37-77: Add prop validation for required fields.

Consider adding runtime validation for required props to prevent potential runtime errors.

+import { z } from "zod";

+const ReleaseProps = z.object({
+  name: z.string(),
+  version: z.string(),
+  releaseId: z.string(),
+  environment: z.object({
+    id: z.string(),
+    name: z.string()
+  }),
+  deployedAt: z.date(),
+  workspaceSlug: z.string(),
+  systemSlug: z.string(),
+  deploymentSlug: z.string(),
+  statuses: z.array(z.string())
+});

 export const Release: React.FC<{
   name: string;
   version: string;
   releaseId: string;
   environment: { id: string; name: string };
   deployedAt: Date;
   workspaceSlug: string;
   systemSlug: string;
   deploymentSlug: string;
   statuses: JobStatusType[];
 }> = (props) => {
+  try {
+    ReleaseProps.parse(props);
+  } catch (error) {
+    console.error('Invalid props:', error);
+    return null;
+  }

109-180: Refactor link href construction for maintainability.

Extract the URL construction logic to improve maintainability and reusability.

+const getReleaseUrl = (params: {
+  workspaceSlug: string;
+  systemSlug: string;
+  deploymentSlug: string;
+  releaseId: string;
+}) => {
+  const { workspaceSlug, systemSlug, deploymentSlug, releaseId } = params;
+  return `/${workspaceSlug}/systems/${systemSlug}/deployments/${deploymentSlug}/releases/${releaseId}`;
+};

 <Link
-  href={`/${workspaceSlug}/systems/${systemSlug}/deployments/${deploymentSlug}/releases/${releaseId}`}
+  href={getReleaseUrl({ workspaceSlug, systemSlug, deploymentSlug, releaseId })}
   className="flex w-full items-center gap-2"
 >
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx (1)

37-71: Consider memoizing API calls to prevent unnecessary re-renders.

The component makes multiple API calls that could benefit from memoization to optimize performance.

+import { useMemo } from 'react';

 const { data: resourceInfo, isLoading: isResourceInfoLoading } =
-  api.resource.byWorkspaceId.list.useQuery(
+  api.resource.byWorkspaceId.list.useQuery(useMemo(() => ({
     {
       workspaceId: workspace.id,
       filter: resourceFilter ?? undefined,
       limit: 0,
     },
-    { enabled: resourceFilter != null },
+    { enabled: resourceFilter != null }
+  }), [workspace.id, resourceFilter]));
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/system-deployment-table/TableDeployments.tsx (2)

74-140: Enhance table accessibility.

The table implementation could benefit from additional ARIA attributes and keyboard navigation support.

-<Table className="w-full min-w-max bg-background">
+<Table 
+  className="w-full min-w-max bg-background"
+  role="grid"
+  aria-label="Deployments across environments"
+>
   <TableHeader className="[&_tr]:border-0">
-    <TableRow className="hover:bg-transparent">
+    <TableRow 
+      className="hover:bg-transparent"
+      role="row"
+    >
       <TableHead 
         className="sticky left-0 z-10 rounded-tl-md py-4 pl-6 backdrop-blur-lg"
+        role="columnheader"
+        aria-sort="none"
       >

92-137: Consider adding empty state handling.

The table should handle cases where there are no deployments to display.

 <TableBody>
+  {deployments.length === 0 && (
+    <TableRow>
+      <TableCell 
+        colSpan={environments.length + 1}
+        className="text-center py-8 text-muted-foreground"
+      >
+        No deployments found
+      </TableCell>
+    </TableRow>
+  )}
   {deployments.map((r, idx) => (
🛑 Comments failed to post (3)
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/StatusIcon.tsx (1)

64-70: ⚠️ Potential issue

Fix potentially incorrect status check for rolling out state.

The variable name isRollingOut suggests a rolling out state, but it checks for JobStatus.Successful. This appears to be incorrect as successful and rolling out are different states.

Apply this diff to fix the status check:

-  const isRollingOut = statuses.some((s) => s === JobStatus.Successful);
+  const isRollingOut = statuses.some((s) => s === JobStatus.RollingOut);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

  const isRollingOut = statuses.some((s) => s === JobStatus.RollingOut);
  if (isRollingOut)
    return (
      <div className="rounded-full bg-green-400 p-1 dark:text-black">
        <IconCalendarTime strokeWidth={2} className="h-4 w-4" />
      </div>
    );
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/ReleaseInfo.tsx (1)

78-108: 🛠️ Refactor suggestion

Add error handling for failed queries.

The component should handle and display query errors gracefully.

 const workspaceId = api.workspace.bySlug.useQuery(workspaceSlug);

 const releaseJobTriggersQ = api.job.config.byWorkspaceId.list.useQuery(
   { workspaceId: workspaceId.data?.id ?? "", filter },
   { enabled: isPresent(workspaceId.data?.id) },
 );

+if (workspaceId.error) {
+  return (
+    <div className="text-sm text-red-500">
+      Failed to load workspace: {workspaceId.error.message}
+    </div>
+  );
+}
+
+if (releaseJobTriggersQ.error) {
+  return (
+    <div className="text-sm text-red-500">
+      Failed to load job triggers: {releaseJobTriggersQ.error.message}
+    </div>
+  );
+}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

  const workspaceId = api.workspace.bySlug.useQuery(workspaceSlug);

  const releaseJobTriggersQ = api.job.config.byWorkspaceId.list.useQuery(
    { workspaceId: workspaceId.data?.id ?? "", filter },
    { enabled: isPresent(workspaceId.data?.id) },
  );

  if (workspaceId.error) {
    return (
      <div className="text-sm text-red-500">
        Failed to load workspace: {workspaceId.error.message}
      </div>
    );
  }

  if (releaseJobTriggersQ.error) {
    return (
      <div className="text-sm text-red-500">
        Failed to load job triggers: {releaseJobTriggersQ.error.message}
      </div>
    );
  }

  const releaseJobTriggers = releaseJobTriggersQ.data ?? [];

  const latestJobsByResource = _.chain(releaseJobTriggers)
    .groupBy((r) => r.resource.id)
    .mapValues((triggers) =>
      _.maxBy(triggers, (t) => new Date(t.job.createdAt)),
    )
    .values()
    .compact()
    .value();

  const data = _.chain(latestJobsByResource)
    .groupBy((r) => r.job.status)
    .entries()
    .map(([name, value]) => ({ name, count: value.length }))
    .push(...Object.keys(statusColor).map((k) => ({ name: k, count: 0 })))
    .unionBy((r) => r.name)
    .sortBy((r) => getStatusColor(r.name))
    .value();

  const configuredWithMessages = releaseJobTriggers.filter((d) =>
    [d.job, d.resource, d.job.message].every(isPresent),
  );
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx (1)

185-192: 🛠️ Refactor suggestion

Add error handling for deployment mutation.

The deployment mutation lacks error handling, which could lead to a poor user experience if the deployment fails.

 onClick={() =>
   deploy
     .mutateAsync({
       environmentId: environment.id,
       releaseId: release.id,
     })
     .then(() => router.refresh())
+    .catch((error) => {
+      console.error('Deployment failed:', error);
+      // Add your error notification system here
+      // Example: toast.error('Failed to deploy: ' + error.message);
+    })
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

        onClick={() =>
          deploy
            .mutateAsync({
              environmentId: environment.id,
              releaseId: release.id,
            })
            .then(() => router.refresh())
            .catch((error) => {
              console.error('Deployment failed:', error);
              // Add your error notification system here
              // Example: toast.error('Failed to deploy: ' + error.message);
            })
        }

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(sidebar)/deployments/TableDeployments.tsx (1)

32-72: Consider optimizing workspace data fetching.

The component fetches workspace data using api.workspace.bySlug.useQuery even though the workspace object is available in the parent component (passed to DeploymentTable). Consider passing the workspace ID directly to avoid unnecessary API calls.

 const EnvIcon: React.FC<{
   environment: Environment;
   workspaceSlug: string;
   systemSlug: string;
+  workspaceId: string;
   className?: string;
-}> = ({ environment: env, workspaceSlug, systemSlug, className }) => {
-  const { data: workspace, isLoading: isWorkspaceLoading } =
-    api.workspace.bySlug.useQuery(workspaceSlug);
-  const workspaceId = workspace?.id ?? "";
+}> = ({ environment: env, workspaceSlug, systemSlug, workspaceId, className }) => {
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/StatusIcon.tsx (1)

21-83: Refactor duplicate styling.

The rounded-full, padding, and dark mode styling is duplicated across all status divs. Consider extracting these common styles to improve maintainability.

+  const baseStyles = "rounded-full p-1 dark:text-black";
+  const getStatusStyles = (color: string) => `${baseStyles} bg-${color}-400`;
+
   if (inProgress)
     return (
-      <div className="animate-spin rounded-full bg-blue-400 p-1 dark:text-black">
+      <div className={`${getStatusStyles('blue')} animate-spin`}>
         <IconLoader2 strokeWidth={2} className="h-4 w-4" />
       </div>
     );
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba44dbb and bd7f9f7.

📒 Files selected for processing (23)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/SystemDeploymentTable.tsx (0 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/checks/flow-diagram/ApprovalCheck.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/jobs/release-table/EnvironmentApprovalRow.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/DeploymentCTA.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/DeploymentPageContent.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/release-cell/ReleaseEnvironmentCell.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/release-cell/TableCells.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(sidebar)/deployments/TableDeployments.tsx (3 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(sidebar)/settings/page.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/charts/DeploymentBarChart.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/dropdown/DeploymentOptionsDropdown.tsx (3 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/ReleaseInfo.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/StatusIcon.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/system-deployment-table/SystemDeploymentTable.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/system-deployment-table/TableDeployments.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/page.tsx (1 hunks)
  • packages/api/src/router/deployment.ts (1 hunks)
  • packages/api/src/router/release-deploy.ts (1 hunks)
  • packages/api/src/router/release.ts (1 hunks)
  • packages/db/drizzle/0072_dapper_sphinx.sql (1 hunks)
  • packages/db/drizzle/meta/_journal.json (1 hunks)
  • packages/db/src/schema/release.ts (2 hunks)
💤 Files with no reviewable changes (1)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/SystemDeploymentTable.tsx
🚧 Files skipped from review as they are similar to previous changes (18)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/charts/DeploymentBarChart.tsx
  • packages/db/drizzle/0072_dapper_sphinx.sql
  • packages/api/src/router/release-deploy.ts
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/page.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/checks/flow-diagram/ApprovalCheck.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/jobs/release-table/EnvironmentApprovalRow.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/release-cell/ReleaseEnvironmentCell.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(sidebar)/settings/page.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/DeploymentCTA.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/DeploymentPageContent.tsx
  • packages/db/drizzle/meta/_journal.json
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/system-deployment-table/SystemDeploymentTable.tsx
  • packages/api/src/router/release.ts
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/system-deployment-table/TableDeployments.tsx
  • packages/db/src/schema/release.ts
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(sidebar)/releases/release-cell/TableCells.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/ReleaseInfo.tsx
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{ts,tsx}`: **Note on Error Handling:** Avoid strict en...

**/*.{ts,tsx}: Note on Error Handling:
Avoid strict enforcement of try/catch blocks. Code may use early returns, Promise chains (.then().catch()), or other patterns for error handling. These are acceptable as long as they maintain clarity and predictability.

  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(sidebar)/deployments/TableDeployments.tsx
  • packages/api/src/router/deployment.ts
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/dropdown/DeploymentOptionsDropdown.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/StatusIcon.tsx
🧠 Learnings (1)
packages/api/src/router/deployment.ts (1)
Learnt from: adityachoudhari26
PR: ctrlplanedev/ctrlplane#181
File: packages/api/src/router/deployment.ts:116-131
Timestamp: 2024-11-12T09:55:38.456Z
Learning: In `packages/api/src/router/deployment.ts`, the `list.byDeploymentId` procedure requires multiple database queries due to limitations of the `releaseMatchesCondition` function.
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Typecheck
  • GitHub Check: Lint
  • GitHub Check: build (linux/amd64)
🔇 Additional comments (10)
packages/api/src/router/deployment.ts (2)

558-559: LGTM! Inner join ensures data consistency.

The addition of the inner join with the system table ensures that only deployments with valid system references are returned.


565-567: LGTM! Simplified system property assignment.

The direct assignment of the system property from the join result maintains type safety and improves readability.

apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/dropdown/DeploymentOptionsDropdown.tsx (2)

4-9: LGTM! Clean and well-organized imports.

The imports are properly organized, with icons grouped together and components separated appropriately.

Also applies to: 20-20


46-57: LGTM! Well-implemented dropdown menu item.

The new "New Release" option is well-integrated into the dropdown menu, following the established patterns for styling, event handling, and component structure.

apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(sidebar)/deployments/TableDeployments.tsx (3)

3-16: LGTM! Clean and well-organized imports.

The imports and type definitions are properly structured and follow consistent patterns.


18-30: LGTM! Well-structured reusable component.

The Icon component is well-designed with proper type definitions and consistent styling.


74-153: LGTM! Well-structured table component.

The DeploymentTable component is well-implemented with:

  • Clean and organized structure
  • Proper handling of responsive design
  • Good use of accessibility attributes
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/StatusIcon.tsx (3)

1-14: LGTM! Well-organized imports.

The imports are clean, specific, and all are utilized within the component.


15-17: LGTM! Clean component definition.

The component interface is well-typed and focused on its specific purpose.


15-17: Handle empty status array.

The component doesn't explicitly handle the case when the status array is empty. Consider adding a default state or prop validation.

 export const StatusIcon: React.FC<{
   statuses: JobStatusType[];
-}> = ({ statuses }) => {
+}> = ({ statuses = [] }) => {
+  if (statuses.length === 0) {
+    return (
+      <div className="rounded-full bg-neutral-400 p-1 dark:text-black">
+        <IconCircleX strokeWidth={2} className="h-4 w-4" />
+      </div>
+    );
+  }

import Link from "next/link";
import { IconLoader2 } from "@tabler/icons-react";

import { cn } from "@ctrlplane/ui";
import { Badge } from "@ctrlplane/ui/badge";

import { LazyReleaseEnvironmentCell } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/release-cell/ReleaseEnvironmentCell";
import { DeploymentOptionsDropdown } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/dropdown/DeploymentOptionsDropdown";
import { LazyDeploymentEnvironmentCell } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix incorrect import path for LazyDeploymentEnvironmentCell.

The import path and the imported component name don't match. The path ends with DeploymentEnvironmentCell.tsx but imports LazyDeploymentEnvironmentCell.

-import { LazyDeploymentEnvironmentCell } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell";
+import { LazyDeploymentEnvironmentCell } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/LazyDeploymentEnvironmentCell";
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import { LazyDeploymentEnvironmentCell } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell";
import { LazyDeploymentEnvironmentCell } from "~/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/LazyDeploymentEnvironmentCell";

Comment on lines +64 to +70
const isRollingOut = statuses.some((s) => s === JobStatus.Successful);
if (isRollingOut)
return (
<div className="rounded-full bg-green-400 p-1 dark:text-black">
<IconCalendarTime strokeWidth={2} className="h-4 w-4" />
</div>
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix potential status check conflict.

The isRollingOut check at line 64 uses some with Successful status, which could conflict with the isComplete check at line 56. This means that if all statuses are successful, both conditions will be true, but only the first one (isComplete) will be rendered due to the early return pattern.

Consider checking specifically for a mix of successful and non-successful statuses for the rolling out state.

-  const isRollingOut = statuses.some((s) => s === JobStatus.Successful);
+  const isRollingOut = statuses.some((s) => s === JobStatus.Successful) && 
+    !statuses.every((s) => s === JobStatus.Successful);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const isRollingOut = statuses.some((s) => s === JobStatus.Successful);
if (isRollingOut)
return (
<div className="rounded-full bg-green-400 p-1 dark:text-black">
<IconCalendarTime strokeWidth={2} className="h-4 w-4" />
</div>
);
const isRollingOut = statuses.some((s) => s === JobStatus.Successful) &&
!statuses.every((s) => s === JobStatus.Successful);
if (isRollingOut)
return (
<div className="rounded-full bg-green-400 p-1 dark:text-black">
<IconCalendarTime strokeWidth={2} className="h-4 w-4" />
</div>
);

@@ -0,0 +1 @@
CREATE INDEX IF NOT EXISTS "release_created_at_idx" ON "release" USING btree ("created_at");
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my query times went down by like half when I added this

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx (1)

152-185: Improve error handling for async deploy actions.
The deploy.mutateAsync call doesn’t provide any user feedback upon failure. Consider catching errors to display a toast or error message so users are informed if deployment fails.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bd7f9f7 and 2c23c98.

📒 Files selected for processing (5)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/checks/flow-diagram/ApprovalCheck.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/jobs/release-table/EnvironmentApprovalRow.tsx (1 hunks)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx (1 hunks)
  • packages/api/src/router/release.ts (3 hunks)
  • packages/db/drizzle/meta/_journal.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/checks/flow-diagram/ApprovalCheck.tsx
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/(raw)/deployments/[deploymentSlug]/(raw)/releases/[releaseId]/jobs/release-table/EnvironmentApprovalRow.tsx
  • packages/db/drizzle/meta/_journal.json
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{ts,tsx}`: **Note on Error Handling:** Avoid strict en...

**/*.{ts,tsx}: Note on Error Handling:
Avoid strict enforcement of try/catch blocks. Code may use early returns, Promise chains (.then().catch()), or other patterns for error handling. These are acceptable as long as they maintain clarity and predictability.

  • packages/api/src/router/release.ts
  • apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx
🧠 Learnings (1)
packages/api/src/router/release.ts (1)
Learnt from: adityachoudhari26
PR: ctrlplanedev/ctrlplane#181
File: packages/api/src/router/deployment.ts:116-131
Timestamp: 2024-11-12T09:55:38.456Z
Learning: In `packages/api/src/router/deployment.ts`, the `list.byDeploymentId` procedure requires multiple database queries due to limitations of the `releaseMatchesCondition` function.
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Typecheck
  • GitHub Check: Lint
  • GitHub Check: build (linux/amd64)
🔇 Additional comments (3)
packages/api/src/router/release.ts (1)

23-34: Looks good on these new imports.
No immediate issues with adding environmentPolicyApproval, resourceMatchesMetadata, and system imports. They are used appropriately below in the new procedure and appear consistent with the rest of the schema-based imports.

apps/webservice/src/app/[workspaceSlug]/(appv2)/systems/[systemSlug]/_components/deployments/environment-cell/DeploymentEnvironmentCell.tsx (2)

82-86: Verify the deployment detection logic.
You currently consider the environment “already deployed” if there’s at least one job status (statuses.length > 0). Verify that this condition truly represents a fully deployed environment (e.g., whether a single failed or incomplete job should still count as “already deployed”).


108-119: Consider handling other release statuses or transitions.
You handle “Building” and “Failed” states, but if future statuses (e.g., “Pending”) are introduced, the user flow might not be clear. Consider clarifying how new or unexpected statuses should be rendered.

Comment on lines +431 to +530
byDeploymentAndEnvironment: protectedProcedure
.input(
z.object({
deploymentId: z.string().uuid(),
environmentId: z.string().uuid(),
}),
)
.meta({
authorizationCheck: async ({ canUser, input }) => {
const { deploymentId, environmentId } = input;
const deploymentAuthzPromise = canUser
.perform(Permission.DeploymentGet)
.on({ type: "deployment", id: deploymentId });
const environmentAuthzPromise = canUser
.perform(Permission.EnvironmentGet)
.on({ type: "environment", id: environmentId });
const [deployment, environment] = await Promise.all([
deploymentAuthzPromise,
environmentAuthzPromise,
]);
return deployment && environment;
},
})
.query(async ({ ctx, input }) => {
const { deploymentId, environmentId } = input;

const env = await ctx.db
.select()
.from(environment)
.innerJoin(system, eq(environment.systemId, system.id))
.innerJoin(
environmentPolicy,
eq(environment.policyId, environmentPolicy.id),
)
.leftJoin(
environmentPolicyReleaseChannel,
eq(environmentPolicyReleaseChannel.policyId, environmentPolicy.id),
)
.leftJoin(
releaseChannel,
and(
eq(environmentPolicyReleaseChannel.channelId, releaseChannel.id),
eq(environmentPolicyReleaseChannel.deploymentId, deploymentId),
),
)
.where(eq(environment.id, environmentId))
.then(takeFirst);

const rel = await ctx.db
.select()
.from(release)
.leftJoin(
environmentPolicyApproval,
and(
eq(environmentPolicyApproval.releaseId, release.id),
eq(environmentPolicyApproval.policyId, env.environment.policyId),
),
)
.where(
and(
eq(release.deploymentId, deploymentId),
env.release_channel != null
? releaseMatchesCondition(
ctx.db,
env.release_channel.releaseFilter,
)
: undefined,
),
)
.orderBy(desc(release.createdAt))
.limit(1)
.then(takeFirstOrNull);

if (rel == null) return null;

if (env.environment.resourceFilter == null)
return {
...rel.release,
approval: rel.environment_policy_approval,
resourceCount: 0,
};

const resourceCount = await ctx.db
.select({ count: count() })
.from(resource)
.where(
and(
eq(resource.workspaceId, env.system.workspaceId),
resourceMatchesMetadata(ctx.db, env.environment.resourceFilter),
isNull(resource.deletedAt),
),
)
.then(takeFirst);

return {
...rel.release,
approval: rel.environment_policy_approval,
resourceCount: resourceCount.count,
};
}),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Guard against null environment lookup to avoid runtime error.
If the environment is not found or the policy is missing, env will be undefined. Subsequent references like env.environment.resourceFilter will result in a runtime error. Consider an early return when env is null/undefined.

Here’s a suggested fix:

   .where(eq(environment.id, environmentId))
   .then(takeFirst);

+  if (!env) {
+    return null;
+  }

   const rel = await ctx.db
     .select()
     ...
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
byDeploymentAndEnvironment: protectedProcedure
.input(
z.object({
deploymentId: z.string().uuid(),
environmentId: z.string().uuid(),
}),
)
.meta({
authorizationCheck: async ({ canUser, input }) => {
const { deploymentId, environmentId } = input;
const deploymentAuthzPromise = canUser
.perform(Permission.DeploymentGet)
.on({ type: "deployment", id: deploymentId });
const environmentAuthzPromise = canUser
.perform(Permission.EnvironmentGet)
.on({ type: "environment", id: environmentId });
const [deployment, environment] = await Promise.all([
deploymentAuthzPromise,
environmentAuthzPromise,
]);
return deployment && environment;
},
})
.query(async ({ ctx, input }) => {
const { deploymentId, environmentId } = input;
const env = await ctx.db
.select()
.from(environment)
.innerJoin(system, eq(environment.systemId, system.id))
.innerJoin(
environmentPolicy,
eq(environment.policyId, environmentPolicy.id),
)
.leftJoin(
environmentPolicyReleaseChannel,
eq(environmentPolicyReleaseChannel.policyId, environmentPolicy.id),
)
.leftJoin(
releaseChannel,
and(
eq(environmentPolicyReleaseChannel.channelId, releaseChannel.id),
eq(environmentPolicyReleaseChannel.deploymentId, deploymentId),
),
)
.where(eq(environment.id, environmentId))
.then(takeFirst);
const rel = await ctx.db
.select()
.from(release)
.leftJoin(
environmentPolicyApproval,
and(
eq(environmentPolicyApproval.releaseId, release.id),
eq(environmentPolicyApproval.policyId, env.environment.policyId),
),
)
.where(
and(
eq(release.deploymentId, deploymentId),
env.release_channel != null
? releaseMatchesCondition(
ctx.db,
env.release_channel.releaseFilter,
)
: undefined,
),
)
.orderBy(desc(release.createdAt))
.limit(1)
.then(takeFirstOrNull);
if (rel == null) return null;
if (env.environment.resourceFilter == null)
return {
...rel.release,
approval: rel.environment_policy_approval,
resourceCount: 0,
};
const resourceCount = await ctx.db
.select({ count: count() })
.from(resource)
.where(
and(
eq(resource.workspaceId, env.system.workspaceId),
resourceMatchesMetadata(ctx.db, env.environment.resourceFilter),
isNull(resource.deletedAt),
),
)
.then(takeFirst);
return {
...rel.release,
approval: rel.environment_policy_approval,
resourceCount: resourceCount.count,
};
}),
byDeploymentAndEnvironment: protectedProcedure
.input(
z.object({
deploymentId: z.string().uuid(),
environmentId: z.string().uuid(),
}),
)
.meta({
authorizationCheck: async ({ canUser, input }) => {
const { deploymentId, environmentId } = input;
const deploymentAuthzPromise = canUser
.perform(Permission.DeploymentGet)
.on({ type: "deployment", id: deploymentId });
const environmentAuthzPromise = canUser
.perform(Permission.EnvironmentGet)
.on({ type: "environment", id: environmentId });
const [deployment, environment] = await Promise.all([
deploymentAuthzPromise,
environmentAuthzPromise,
]);
return deployment && environment;
},
})
.query(async ({ ctx, input }) => {
const { deploymentId, environmentId } = input;
const env = await ctx.db
.select()
.from(environment)
.innerJoin(system, eq(environment.systemId, system.id))
.innerJoin(
environmentPolicy,
eq(environment.policyId, environmentPolicy.id),
)
.leftJoin(
environmentPolicyReleaseChannel,
eq(environmentPolicyReleaseChannel.policyId, environmentPolicy.id),
)
.leftJoin(
releaseChannel,
and(
eq(environmentPolicyReleaseChannel.channelId, releaseChannel.id),
eq(environmentPolicyReleaseChannel.deploymentId, deploymentId),
),
)
.where(eq(environment.id, environmentId))
.then(takeFirst);
if (!env) {
return null;
}
const rel = await ctx.db
.select()
.from(release)
.leftJoin(
environmentPolicyApproval,
and(
eq(environmentPolicyApproval.releaseId, release.id),
eq(environmentPolicyApproval.policyId, env.environment.policyId),
),
)
.where(
and(
eq(release.deploymentId, deploymentId),
env.release_channel != null
? releaseMatchesCondition(
ctx.db,
env.release_channel.releaseFilter,
)
: undefined,
),
)
.orderBy(desc(release.createdAt))
.limit(1)
.then(takeFirstOrNull);
if (rel == null) return null;
if (env.environment.resourceFilter == null)
return {
...rel.release,
approval: rel.environment_policy_approval,
resourceCount: 0,
};
const resourceCount = await ctx.db
.select({ count: count() })
.from(resource)
.where(
and(
eq(resource.workspaceId, env.system.workspaceId),
resourceMatchesMetadata(ctx.db, env.environment.resourceFilter),
isNull(resource.deletedAt),
),
)
.then(takeFirst);
return {
...rel.release,
approval: rel.environment_policy_approval,
resourceCount: resourceCount.count,
};
}),

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant