nitor 1.5.0 → 1.7.0

package/services/utils.js

@@ -31,6 +31,8 @@ const zohoConfig = {
   token: process.env.ZOHO_TOKEN,
   url: process.env.ZOHO_URI,
   userId: process.env.ZOHO_USERID,
+  workspace: process.env.ZOHO_WORKSPACE,
+  projectPrefix: process.env.ZOHO_PROJECT_PREFIX,
 };
 const keyMap = {
   components: 'components',
@@ -61,6 +63,10 @@ const keyMap = {
   do: 'docker',
   sprint: 'sprint',
   s: 'sprint',
+  state: 'state',
+  st: 'state',
+  search: 'search',
+  q: 'search',
 };
 const projectMap = {
   portal: 'medica-portal',
@@ -388,6 +394,23 @@ const box = {
 // Loading spinner frames
 const spinnerFrames = ['⠋', '⠙', '⠹', '⠸', '⠼', '⠴', '⠦', '⠧', '⠇', '⠏'];
 
+// Match CSI (SGR etc.) and OSC 8 hyperlink escape sequences so we can compute
+// the visible width of strings that contain ANSI styling or terminal links.
+// eslint-disable-next-line no-control-regex
+const ANSI_REGEX = /\x1B\]8;[^\x07\x1B]*(?:\x07|\x1B\\)|\x1B\[[0-9;]*[A-Za-z]/g;
+const stripAnsi = (s) => String(s ?? '').replace(ANSI_REGEX, '');
+const visibleLength = (s) => stripAnsi(s).length;
+
+/**
+ * Wrap text in an OSC 8 terminal hyperlink so supporting terminals render it
+ * as a clickable link.
+ */
+const makeLink = (url, text = url) => {
+  if (!url) return String(text ?? '');
+
+  return `\x1B]8;;${url}\x07${text}\x1B]8;;\x07`;
+};
+
 /**
  * Create a loading spinner for async operations
  * @param {string} message - Loading message to display
@@ -491,24 +514,27 @@ const printTable = (data, options = {}) => {
     });
   }
 
-  // Calculate column widths
+  // Calculate column widths (ignore ANSI/hyperlink escapes when measuring)
   const colWidths = {};
   columns.forEach((col) => {
     const headerLen = col.length;
-    const maxDataLen = Math.max(
-      ...filteredData.map((row) => String(row[col] ?? '').length),
-      headerLen,
-    );
+    const maxDataLen = Math.max(...filteredData.map((row) => visibleLength(row[col])), headerLen);
     colWidths[col] = Math.min(maxDataLen, maxColWidth);
   });
 
-  // Helper to truncate and pad text
+  // Helper to truncate and pad text while preserving ANSI/hyperlink escapes
   const formatCell = (text, width) => {
     const str = String(text ?? '');
-    if (str.length > width) {
-      return str.substring(0, width - 2) + '..';
+    const visible = visibleLength(str);
+
+    if (visible > width) {
+      // Only values without embedded escapes are safely truncatable; for
+      // links/colored values, fall back to stripped text to keep widths sane.
+      const plain = stripAnsi(str);
+      return plain.substring(0, width - 2) + '..';
     }
-    return str.padEnd(width);
+
+    return str + ' '.repeat(width - visible);
   };
 
   // Top border
@@ -623,4 +649,5 @@ module.exports = {
   gitlabConfig,
   printTable,
   createSpinner,
+  makeLink,
 };

package/.commitlintrc.json

@@ -1,10 +0,0 @@
-{
-  "extends": ["@commitlint/config-angular"],
-  "rules": {
-    "subject-case": [
-      2,
-      "always",
-      ["sentence-case", "start-case", "pascal-case", "upper-case", "lower-case"]
-    ]
-  }
-}

package/.editorconfig

@@ -1,16 +0,0 @@
-# Editor configuration, see https://editorconfig.org
-root = true
-
-[*]
-charset = utf-8
-indent_style = space
-indent_size = 2
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-[*.ts]
-quote_type = single
-
-[*.md]
-max_line_length = off
-trim_trailing_whitespace = false

package/.eslintrc.js

@@ -1,29 +0,0 @@
-module.exports = {
-  env: {
-    browser: true,
-    node: true,
-    commonjs: true,
-  },
-  extends: ['eslint:recommended', 'plugin:@typescript-eslint/recommended'],
-  overrides: [
-    {
-      env: {
-        node: true,
-      },
-      files: ['.eslintrc.{js,cjs}'],
-      parserOptions: {
-        sourceType: 'script',
-      },
-    },
-  ],
-  parser: '@typescript-eslint/parser',
-  parserOptions: {
-    ecmaVersion: 'latest',
-    sourceType: 'module',
-  },
-  plugins: ['@typescript-eslint'],
-  rules: {
-    '@typescript-eslint/no-unsafe-optional-chain': 'off',
-    '@typescript-eslint/no-var-requires': 'off',
-  },
-};

package/.gitattributes

@@ -1,2 +0,0 @@
-package-lock.json   -diff -merge
-package-lock.json    linguist-generated=true

package/.prettierrc

@@ -1,5 +0,0 @@
-{
-  "singleQuote": true,
-  "trailingComma": "all",
-  "printWidth": 100
-}

package/.releaserc.json

@@ -1,34 +0,0 @@
-{
-  "branches": ["master"],
-  "plugins": [
-    [
-      "@semantic-release/commit-analyzer",
-      {
-        "preset": "angular",
-        "releaseRules": [
-          { "type": "feat", "release": "minor" },
-          { "type": "fix", "release": "patch" },
-          { "type": "docs", "release": false },
-          { "type": "style", "release": false },
-          { "type": "refactor", "release": "patch" },
-          { "type": "perf", "release": "patch" },
-          { "type": "breaking", "release": "major" }
-        ],
-        "parserOpts": {
-          "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES"]
-        }
-      }
-    ],
-    "@semantic-release/release-notes-generator",
-    "@semantic-release/changelog",
-    "@semantic-release/npm",
-    "@semantic-release/github",
-    [
-      "@semantic-release/git",
-      {
-        "assets": ["CHANGELOG.md", "package.json"],
-        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
-      }
-    ]
-  ]
-}

package/docs/AUTOCOMPLETE.md

@@ -1,136 +0,0 @@
-# Autocomplete Setup Guide
-
-## Overview
-
-Nitor supports shell autocomplete for commands, options, and values using the `omelette` library.
-
-## Setup
-
-### 1. Install Autocomplete
-
-After installing nitor globally, run:
-
-```bash
-nitor completion
-```
-
-### 2. Activate Autocomplete
-
-Restart your terminal or source your shell configuration:
-
-**For Bash:**
-
-```bash
-source ~/.bashrc
-```
-
-**For Zsh:**
-
-```bash
-source ~/.zshrc
-```
-
-**For Fish:**
-
-```bash
-source ~/.config/fish/config.fish
-```
-
-## Usage
-
-Once autocomplete is enabled, press `Tab` to see suggestions:
-
-### Command Completion
-
-```bash
-nitor <Tab>
-# Shows: build, deploy, build-deploy, create-branch, review, refactor, backup, merge, cleanup,
-#        time-init, time-switch, time-add, time-update, time-delete, time-stats, time-entries,
-#        time-zoho, time-gitlab, time-merge, version, help
-```
-
-### Option Completion
-
-```bash
-nitor build -<Tab>
-# Shows: -project, -p, -components, -c, -instance, -i, -help, --h
-```
-
-### Value Completion
-
-```bash
-nitor build -project <Tab>
-# Shows: portal, gateway, phr, configService, healthRecords, centralAuth, mpi, phrAdminBackend, phrAdminClient, terminologyService
-
-nitor build -instance <Tab>
-# Shows: dev, qa, pilot
-
-nitor create-branch -type <Tab>
-# Shows: feat, fix
-```
-
-## Supported Completions
-
-### Commands
-
-- `build`, `deploy`, `build-deploy`
-- `create-branch`, `review`, `refactor`
-- `backup`, `merge`, `cleanup`
-- `time-init`, `time-switch`, `time-add`, `time-update`, `time-delete`
-- `time-stats`, `time-entries`, `time-zoho`, `time-gitlab`, `time-merge`
-- `version`, `help`, `completion`
-
-### Options
-
-- Project names: `portal`, `gateway`, `phr`, etc.
-- Components: `client`, `administration`, `provider`, `rest-api`
-- Instances: `dev`, `qa`, `pilot`
-- Branch types: `feat`, `fix`
-- Repository names: `portalClient`, `portalBackend`, etc.
-
-## Troubleshooting
-
-### Autocomplete Not Working
-
-1. **Verify installation:**
-
-   ```bash
-   nitor completion
-   ```
-
-2. **Check shell configuration:**
-
-   - Bash: `~/.bashrc`
-   - Zsh: `~/.zshrc`
-   - Fish: `~/.config/fish/config.fish`
-
-3. **Reload shell:**
-   ```bash
-   exec $SHELL
-   ```
-
-### Manual Setup
-
-If automatic setup doesn't work, add this to your shell configuration:
-
-**Bash (~/.bashrc):**
-
-```bash
-# nitor autocomplete
-if type nitor > /dev/null 2>&1; then
-  eval "$(nitor --completion)"
-fi
-```
-
-**Zsh (~/.zshrc):**
-
-```bash
-# nitor autocomplete
-if type nitor > /dev/null 2>&1; then
-  eval "$(nitor --completion)"
-fi
-```
-
-## Uninstall Autocomplete
-
-To remove autocomplete, edit your shell configuration file and remove the nitor completion lines, then reload your shell.

package/docs/BACKUP.md

@@ -1,343 +0,0 @@
-# Backup Command Guide
-
-## Overview
-
-The `backup` command creates MongoDB database backups for specified projects and components, ensuring data safety and recovery options.
-
-## Usage
-
-### Basic Syntax
-
-```bash
-nitor backup -project <project name> -components <component name>
-```
-
-### Short Form
-
-```bash
-nitor backup -p <project name> -c <component name>
-```
-
-## Options
-
-| Option         | Short   | Description    | Required |
-| -------------- | ------- | -------------- | -------- |
-| `--project`    | `-p`    | Project name   | Yes      |
-| `--components` | `-c`    | Component name | Optional |
-| `--help`       | `-help` | Show help      | -        |
-
-## Examples
-
-### Backup Config Service
-
-```bash
-nitor backup -p configService
-```
-
-### Backup Medica Central Auth
-
-```bash
-nitor backup -project medicaCentralAuth
-```
-
-### Backup Medica Portal
-
-```bash
-nitor backup -p medicaPortal
-```
-
-### Backup PHR System
-
-```bash
-nitor backup -project phr
-```
-
-## Supported Projects
-
-- **configService** - Configuration service database
-- **medicaCentralAuth** - Medica central authentication database
-- **medicaPortal** - Medica portal database
-- **phr** - Personal Health Records database
-
-## Backup Process
-
-The backup command will:
-
-1. **Connect to MongoDB**
-
-   - Establishes connection to database server
-   - Authenticates with credentials
-
-2. **Identify Databases**
-
-   - Determines which databases to backup
-   - Based on project and component parameters
-
-3. **Create Backup**
-
-   - Exports database collections
-   - Preserves data structure and relationships
-
-4. **Store Backup**
-
-   - Saves backup to designated location
-   - Includes timestamp in filename
-
-5. **Verify Backup**
-   - Confirms backup completion
-   - Reports backup status
-
-## Backup Location
-
-Backups are typically stored in:
-
-- Project-specific backup directory
-- Timestamped folders for version control
-- Compressed format for space efficiency
-
-## Backup Naming Convention
-
-Backups follow this pattern:
-
-```
-<project>_<component>_<timestamp>.backup
-```
-
-**Examples:**
-
-- `configService_20241115_171030.backup`
-- `medicaPortal_20241115_171030.backup`
-- `phr_20241115_171030.backup`
-
-## When to Backup
-
-### Regular Backups
-
-- **Daily** - For production databases
-- **Before Deployments** - Prior to major changes
-- **Before Migrations** - Before schema updates
-- **Weekly** - For development databases
-
-### Critical Moments
-
-- Before major feature releases
-- Before data migrations
-- Before system upgrades
-- After significant data changes
-
-## Best Practices
-
-### Backup Strategy
-
-1. **Schedule Regular Backups**
-
-   - Automate daily backups
-   - Use cron jobs or schedulers
-
-2. **Test Backups**
-
-   - Regularly verify backup integrity
-   - Practice restoration procedures
-
-3. **Multiple Locations**
-
-   - Store backups in multiple locations
-   - Use cloud storage for redundancy
-
-4. **Retention Policy**
-   - Keep daily backups for 7 days
-   - Keep weekly backups for 1 month
-   - Keep monthly backups for 1 year
-
-### Security
-
-1. **Encrypt Backups**
-
-   - Use encryption for sensitive data
-   - Secure backup storage locations
-
-2. **Access Control**
-
-   - Limit backup access to authorized users
-   - Use strong authentication
-
-3. **Audit Trail**
-   - Log backup operations
-   - Track who created backups
-
-## Restoration
-
-To restore from a backup:
-
-1. **Locate Backup File**
-
-   ```bash
-   ls -la /path/to/backups/
-   ```
-
-2. **Verify Backup Integrity**
-
-   - Check file size
-   - Verify timestamp
-
-3. **Restore Database**
-
-   ```bash
-   mongorestore --archive=<backup-file>
-   ```
-
-4. **Verify Restoration**
-   - Check data integrity
-   - Test application functionality
-
-## Troubleshooting
-
-### Backup Fails to Start
-
-1. **Check MongoDB Connection:**
-
-   - Verify MongoDB is running
-   - Test connection credentials
-   - Check network connectivity
-
-2. **Verify Permissions:**
-
-   - Ensure user has backup privileges
-   - Check file system permissions
-
-3. **Check Disk Space:**
-   ```bash
-   df -h
-   ```
-   - Ensure sufficient space for backup
-
-### Incomplete Backup
-
-If backup completes but seems incomplete:
-
-1. **Check Logs:**
-
-   - Review backup logs for errors
-   - Look for timeout issues
-
-2. **Verify Collections:**
-
-   - List all collections
-   - Compare with backup contents
-
-3. **Retry Backup:**
-   - Run backup again
-   - Use verbose mode for details
-
-### Connection Errors
-
-If you encounter connection errors:
-
-1. **Verify MongoDB Status:**
-
-   ```bash
-   systemctl status mongod
-   ```
-
-2. **Check Credentials:**
-
-   - Verify username and password
-   - Ensure user has proper roles
-
-3. **Test Connection:**
-   ```bash
-   mongo --host <host> --port <port>
-   ```
-
-## Configuration
-
-The backup command requires:
-
-1. **MongoDB Connection Details:**
-
-   - Host and port
-   - Database name
-   - Authentication credentials
-
-2. **Backup Storage:**
-
-   - Backup directory path
-   - Sufficient disk space
-   - Write permissions
-
-3. **Environment Variables:**
-   - MongoDB connection string
-   - Backup configuration
-
-## Automation
-
-### Cron Job Example
-
-```bash
-# Daily backup at 2 AM
-0 2 * * * nitor backup -p configService
-
-# Weekly backup on Sunday at 3 AM
-0 3 * * 0 nitor backup -p medicaPortal
-
-# Monthly backup on 1st at 4 AM
-0 4 1 * * nitor backup -p phr
-```
-
-### Backup Script
-
-```bash
-#!/bin/bash
-# Backup all projects
-
-projects=("configService" "medicaCentralAuth" "medicaPortal" "phr")
-
-for project in "${projects[@]}"; do
-    echo "Backing up $project..."
-    nitor backup -p "$project"
-done
-
-echo "All backups completed!"
-```
-
-## Monitoring
-
-### Backup Verification
-
-1. **Check Backup Size:**
-
-   ```bash
-   ls -lh /path/to/backups/
-   ```
-
-2. **Verify Timestamp:**
-
-   - Ensure backup is recent
-   - Check for stale backups
-
-3. **Test Restoration:**
-   - Periodically test restore process
-   - Verify data integrity
-
-### Alerts
-
-Set up alerts for:
-
-- Backup failures
-- Disk space issues
-- Connection problems
-- Unusual backup sizes
-
-## Getting Help
-
-To see all available options:
-
-```bash
-nitor backup -help
-```
-
-## Related Commands
-
-- `nitor build` - Build before backing up
-- `nitor deploy` - Deploy after backup verification
-- MongoDB tools for manual backup/restore