@adinsure-ops/ops-cli 4.8.3 → 5.0.0-rc4

package/CHANGELOGS.md

@@ -1,8 +1,24 @@
 # Changelogs
 
+## 5.0.0-rc4: 2023-09-05
+
+- Added --keep flag to the download:studio command
+
+## 5.0.0-rc3: 2023-09-01
+
+- Bugfixes
+- Security patching: the project was migrated to a new oclif framework from the old one
+- Performace tuning
+- [DEPRECATED] Deprecation and removal of the prepare-content command
+
+## 4.8.3: 2023-08-22
+
+- Bugfixes; sql command was fixed so that even when Extend was not used it required its parameters
+- Security patches in library dependencies
+
 ## 4.8.2: 2023-07-28
 
-- sql command can now generate a template for mssql and oracle, for extending an sql table with a column
+- Sql command can now generate a template for mssql and oracle, for extending an sql table with a column
 
 ## 4.8.1: 2023-06-01
 
@@ -18,45 +34,45 @@
 
 ## 4.7.0: 2023-03-22
 
-- fixed bug in `download:studio` when flag `-i` was always required in case we used `-o` flag
-- download of signalr is now also supported
-- improved description for download topic, it now displays information on downloading individual components
-- update command is no longer supported. Instead the update available warning provides information on available update options
+- Fixed bug in `download:studio` when flag `-i` was always required in case we used `-o` flag
+- Download of signalr is now also supported
+- Improved description for download topic, it now displays information on downloading individual components
+- Update command is no longer supported. Instead the update available warning provides information on available update options
 
 ## 4.6.0: 2023-02-15
 
-- doctor no longer checks for `vsts-npm-auth` package
-- when installing studio you can pass parameter `s` to skip installation in case the selected version is already installed
+- Doctor no longer checks for `vsts-npm-auth` package
+- When installing studio you can pass parameter `s` to skip installation in case the selected version is already installed
 
 ## 4.5.2: 2023-01-12
 
-- limit description length for sql scripts
+- Limit description length for sql scripts
 
 ## 4.5.1: 2022-12-13
 
-- fixed release version for windows and linux packages
+- Fixed release version for windows and linux packages
 
 ## 4.5.0: 2022-10-05
 
-- add `--major` flag for sql script generation
-- add `SQL_SCRIPT_VERSION` to force script generation
+- Add `--major` flag for sql script generation
+- Add `SQL_SCRIPT_VERSION` to force script generation
 
 ## 4.4.0: 2022-10-03
 
-- added parameters for offline sql script creation
-- ability to recover from prerelease tag when creating db scripts
+- Added parameters for offline sql script creation
+- Ability to recover from prerelease tag when creating db scripts
 
 ## 4.3.0: 2022-07-27
 
-- added command `npm:dependency-update` to update dependencies on packages in workspace defined by filter
-- added command `nuget:dependency-update` to update dependencies on packages in workspace defined by filter
-- improve error handling in translation fetching
-- improve warning output when npm publish fails
+- Added command `npm:dependency-update` to update dependencies on packages in workspace defined by filter
+- Added command `nuget:dependency-update` to update dependencies on packages in workspace defined by filter
+- Improve error handling in translation fetching
+- Improve warning output when npm publish fails
 
 ## 4.2.0: 2022-07-15
 
-- added command `gitlab:get-tag-pipeline` to track pipeline status and wait for pipeline to finish
-- added `--outputVersionOnly` to `gitlab:next-nightly-tag` to output only version
+- Added command `gitlab:get-tag-pipeline` to track pipeline status and wait for pipeline to finish
+- Added `--outputVersionOnly` to `gitlab:next-nightly-tag` to output only version
 
 ## 4.1.0: 2022-06-15
 
@@ -64,55 +80,55 @@
 
 ## 4.0.0: 2021-05-31
 
-- new auth options
+- New auth options
 - [DEPRECATED] `--servicePrincipal` login is no longer available or required. 'AZURE_CLIENT_ID' and 'AZURE_CLIENT_SECRET' environment variables are required with every command in order to use service principal.
 
 ## 3.9.0: 2021-05-30
 
-- additional options for translations output filename
+- Additional options for translations output filename
 
 ## 3.8.1: 2021-05-17
 
-- fix GitLab next nightly tag when tags with `test` and `qa` annotation exists
+- Fix GitLab next nightly tag when tags with `test` and `qa` annotation exists
 
 ## 3.8.0: 2021-05-05
 
-- added GitLab next nightly tag
+- Added GitLab next nightly tag
 
 ## 3.7.0: 2021-04-28
 
-- added download commands for AdInsure Server, Client, IdentityServer and Scheduler
+- Added download commands for AdInsure Server, Client, IdentityServer and Scheduler
 
 ## 3.6.1: 2021-12-02
 
-- improve workspace search pattern for npm publish
+- Improve workspace search pattern for npm publish
 
 ## 3.6.0: 2021-11-30
 
-- add ability to transform files with prepare-content
+- Add ability to transform files with prepare-content
 
 ## 3.5.0: 2021-11-24
 
-- renaming prepare-content command
+- Renaming prepare-content command
 
 ## 3.4.0: 2021-10-24
 
-- added Jira command for listing labels and setting them
-- added Jira command for listing issue
+- Added Jira command for listing labels and setting them
+- Added Jira command for listing issue
 
 ## 3.3.1: 2021-10-16
 
-- exclude should be optional for npm:publish
+- Exclude should be optional for npm:publish
 
 ## 3.3.0: 2021-10-14
 
-- introduced npm check command
-- introcuced npm publish command
-- introduced doctor command
-- introduced download:platform and download:studio command
+- Introduced npm check command
+- Introcuced npm publish command
+- Introduced doctor command
+- Introduced download:platform and download:studio command
 
 ## 3.2.4: 2021-10-09
 
-- ignore VERSION file when using 'new' command
+- Ignore VERSION file when using 'new' command
 - Unexpected token in JSON files should not stop execution
-- introduce `--exclude-dir` parameter for `version` command
+- Introduce `--exclude-dir` parameter for `version` command

package/LICENSE

@@ -1 +1 @@
-(c) Copyright 2021 Adacta d.o.o., all rights reserved.
+(c) Copyright 2023 Adacta d.o.o., all rights reserved.

package/README.md

@@ -2,7 +2,7 @@
 
 Operations CLI for supporting AdInsure development processes.
 
-https://www.npmjs.com/package/@adinsure-ops/ops-cli
+<https://www.npmjs.com/package/@adinsure-ops/ops-cli>
 
 ## Install
 
@@ -10,7 +10,7 @@ https://www.npmjs.com/package/@adinsure-ops/ops-cli
 
 ## CLI development
 
-For development you will need **[Node.js](https://nodejs.org/en/)** (recommended 16 LTS, minimal 8.0.0) and **[Yarn](https://yarnpkg.com/en/)** installed. 
+For development you will need **[Node.js](https://nodejs.org/en/)** (recommended 16 LTS, minimal 14.0.0) and **[Yarn](https://yarnpkg.com/en/)** installed.
 
 We recommend **[Visual Studio Code](https://code.visualstudio.com/)** IDE.
 
@@ -26,31 +26,30 @@ You can run and debug commands directly from terminal by running `ops [command]`
 ## Commands
 
 <!-- commands -->
-- [`ops help [COMMAND]`](##ops-help-command)
-- [`ops doctor`](##ops-doctor)
-- [`ops download:client <flags>`](##ops-download:client-<flags>)
-- [`ops download:identity-server <flags>`](##ops-download:identity-server-<flags>)
-- [`ops download:platform <flags>`](##ops-download:platform-<flags>)
-- [`ops download:scheduler <flags>`](##ops-download:scheduler-<flags>)
-- [`ops download:server <flags>`](##ops-download:server-<flags>)
-- [`ops download:signalr <flags>`](##ops-download:signalr-<flags>)
-- [`ops download:studio <flags>`](##ops-download:studio-<flags>)
-- [`ops download:keycloak-scim <flags>`](##ops-download:keycloak-scim-<flags>)
-- [`ops download:jmeter-examples <flags>`](##ops-download:studio-<flags>) 
-- [`ops gitlab:get-tag-pipeline`](##ops-gitlab:get-tag-pipeline)
-- [`ops gitlab:next-nightly-tag`](##ops-gitlab:next-nightly-tag)
-- [`ops log <component> <issue> [options]`](##ops-log-<component>-<issue>-[options])
-- [`ops log:gen [options]`](##ops-log:gen-[options])
-- [`ops log:validate [options]`](##ops-log:validate-[options])
-- [`ops login`](##ops-login)
-- [`ops npm:check-publish`](##ops-npm:check-publish)
-- [`ops npm:publish`](##ops-npm:publish)
-- [`ops npm:dependency-update`](##ops-npm:dependency-update)
-- [`ops nuget:dependency-update`](##ops-nuget:dependency-update)
-- [`ops prepare-content`](##ops-prepare-content)
-- [`ops sql <type> <module> [flags]`](##ops-sql-<type>-<module>-[flags])
-- [`ops translate`](##ops-translate)
-- [`ops version <type> [flags]`](##ops-version-<type>[flags])
+- [`ops help [COMMAND]`](#ops-help-command)
+- [`ops doctor`](#ops-doctor)
+- [`ops download:client <flags>`](#ops-downloadclient-flags)
+- [`ops download:identity-server <flags>`](#ops-downloadidentity-server-flags)
+- [`ops download:platform <flags>`](#ops-downloadplatform-flags)
+- [`ops download:scheduler <flags>`](#ops-downloadscheduler-flags)
+- [`ops download:server <flags>`](#ops-downloadserver-flags)
+- [`ops download:signalr <flags>`](#ops-downloadsignalr-flags)
+- [`ops download:studio <flags>`](#ops-downloadstudio-flags)
+- [`ops download:keycloak-scim <flags>`](#ops-downloadkeycloak-scim-flags)
+- [`ops download:jmeter-examples <flags>`](#ops-downloadstudio-flags)
+- [`ops gitlab:get-tag-pipeline`](#ops-gitlabget-tag-pipeline)
+- [`ops gitlab:next-nightly-tag`](#ops-gitlabnext-nightly-tag)
+- [`ops log <issue> -t <type> -c [component]`](#ops-log-issue-t-type-c-component)
+- [`ops log:gen [options]`](#ops-loggen-options)
+- [`ops log:validate [options]`](#ops-logvalidate-options)
+- [`ops login`](#ops-login)
+- [`ops npm:check-publish`](#ops-npmcheck-publish)
+- [`ops npm:publish`](#ops-npmpublish)
+- [`ops npm:dependency-update`](#ops-npmdependency-update)
+- [`ops nuget:dependency-update`](#ops-nugetdependency-update)
+- [`ops sql <type> <module> [flags]`](#ops-sql-type-module-flags)
+- [`ops translate`](#ops-translate)
+- [`ops version <type> [flags]`](#ops-version-type)
 
 ## `ops help [COMMAND]`
 
@@ -67,7 +66,7 @@ OPTIONS
   --all  see all commands in CLI
 ```
 
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v2.2.0/src\commands\help.ts)_
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v2.2.0/src/commands/help.ts)_
 
 ## `ops doctor`
 
@@ -192,6 +191,7 @@ USAGE
   $ ops download:studio <flags>
 
 OPTIONS
+  -k, --keep             only with install. If passed, it will not remove the vsix file
   -i, --install          install plugin to vscode. save to temp folder and remove vsix after.
   -o, --output=output    [default: ./] output directory
   -s, --skip             only with install. If passed, and desired version is installed it will skip it.
@@ -487,216 +487,6 @@ EXAMPLE
   $ ops nuget:dependency-update 3.4.3 --filter Adacta.AdInsure --exclude Scheduler
 ```
 
-## `ops prepare-content -d <destination> -s [source]`
-
-creates a directory/file structure from `/source` to `/destination</source>` as defined in the `.opsprepare` file. Actual
-destination path for each file will be specified destination path with appended relative path from working directory where command is executed to specified source directory or current directory (if source is not specified). Be careful about using
-`..` notation in target and source paths as it may lead to unpredictable results due to relative path resolving.
-
-> Introduced in version 3.1.0.
-
-```txt
-USAGE
-  $ ops prepare-content -d <destination> -s [source]
-
-
-OPTIONS
-  -d, --destination=destination       path to target directory
-  -s, --source=source                 optional path to source directory containing .opsprepare file, (default: current directory)
-
-EXAMPLES
-$ ops prepare-content -d ./target_directory/
-  copies everything defined in .opsprepare
-  from current directory 
-  to ./target_directory
-
-$ ops prepare-content -d ./target_directory/ -s ./source_directory
-  copies everything defined in ./source_directory/.opsprepare 
-  from ./source_directory/
-  to ./target_directory/source_directory
-
-$ ops prepare-content -d C:\git\target_directory
-  copies everything defined in .opsprepare 
-  from current directory 
-  to C:\git\target_directory
-
-$ ops prepare-content -d C:\git\target_directory -s C:\git\subfolder\subfolder
-  when executed in c:\git it copies everything defined in C:\git\subfolder\subfolder\.opsprepare 
-  from C:\git\subfolder\subfolder
-  to C:\git\target_directory\subfolder\subfolder
-```
-
-### .opsprepare dotfile
-
-The prepare-content command uses `.opsprepare` dotfile as instruction set for content preparation.
-The syntax resembles that of `.gitignore` but differs in how it functions and doesn't support advanced
-pattern matching.
-
-Following operations/transformations are currently supported:
-
-- Copy: copies the file/directory from source path to destination path with same name
-- Transform: transform source file to destination file with same name
-- Removal: remove file/directory (based on source path) from destination path
-
-Before diving into the actual syntax and supported tokens let's look at an example
-of how using `ops prepare-content` creates a target directory structure with files
-based on the specified `.opsprepare` file residing in source directory.
-
-This is the example source directory structure:
-
-```ascii
-src_data
-├── .opsprepare
-├── README.tpl
-├── bin
-│   ├── ops.sh
-│   └── run
-│       └── ops
-├── dist
-│   └── server
-│       └── main.cs
-├── src
-│   ├── commands
-│   │   ├── prepare.ts
-│   │   └── version.ts
-│   ├── config.ts
-│   └── main.ts
-└── transform
-    └── render-tpl.js
-```
-
-Contents of `.opsprepare` file in the `src_data` directory:
-
-```txt
-# Comment
-src
-dist/server
-!src/commands
-!src/config.ts
-src/config.ts {cp:/src/configuration.ts}
-# Another comment
-!bin/run
-README.md {js:/transform/render-tpl.js:render}
-README.tpl {cp:/README.tpl.src}
-```
-
-Running `ops -s src_data -d dst_data` with `src_data/.opsprepare` containing above content
-results in:
-
-```ascii
-dst_data
-└── src_data
-    ├── README.md
-    ├── README.tpl.src
-    ├── dist
-    │   └── server
-    │       └── main.cs
-    └── src
-        ├── main.ts
-        └── src
-            └── configuration.ts
-```
-
-What actually happened:
-
-1. First note that all data was copied into `dst_data/src_data` because `.opsprepare` files relative
-   location to `ops` execution directiory is `src_data`.
-2. `src` directory was copied recursively to destination
-3. `dist/server` directory was copied recursively including its full path path relative to `src_data`
-4. `src/config.ts` file was transformed (copied) to `src/configuration.ts` in the destination
-5. `README.md` file was created at the destination as a result of JavaScript based transformation
-6. `README.tpl` file was transformed (copied) to `README.tpl.src` in the destination
-7. `src/commands` directory was removed from destination
-8. `src/config.ts` file was removed from destination
-9. `bin/run` directory was removed from destination
-
-Note that copying and explicit transformations are performed before any removal operations.
-
-#### Comments
-
-Any line prefixed by `#` is considered a comment and will not result in any file/directory operation.
-
-#### Copy operations
-
-Any file/directory not prefixed by `!` or `#` having explicit transformation defined in `{...}` after
-its name will be copied to the destination with it's full path relative to `ops` execution directory
-to the target directory.
-
-#### Transformation operations
-
-Transformation operations are always specified using curly braces following the source file name. Base
-syntax looks like this:
-
-```txt
-{<transformation type>:<transformation parameters>}
-```
-
-Two types of transformation operations are supported:
-
-- cp: copy transformation which supports renaming of the source file at the destination
-- js: JavasSript based transformation which results in the file containing string returned by the
-  transformation function contained in transformation module.
-
-**cp - copy transformation syntax**
-
-```txt
-{cp:<destination path>}
-
-Examples:
-{cp:/dst/newfilename}
-{cp:dst/newfilenames}
-```
-
-Copy transformation is supported for both files and directories. Source file or directory will be
-copied to the destination path with its new name. The destination will always be relative to the
-destination path of entire `prepare-content` operation therefore paths in the transformation block
-can start with or without the `/` character but using makes the syntax more readable.
-
-**js - JavaScript transformation syntax**
-
-```txt
-{js:<transformation_module_path>:<transformation_function_name>}
-
-Example:
-{js:/transformations/templateRenderer.js:renderEjsTemplate}
-```
-
-JavaScript transformation is supported only for files, not directories.
-
-Transformation module path should be relative to `.opsprepare` file but can start with `/` character
-for better readability. It can export multiple functions though only one can be used in single
-transformation specification.
-
-Transformation function that is defined in the transformation module will be called with a single
-parameter - absolute path of the source file.
-
-Transformation function MUST return a string. This string will become the content of the file on
-destination.
-
-Destination file will be created with the same name as source file and content returned by the
-transformation function. The existence of actual source file will not be validated by the
-`prepare-content` operation (warning is shown if it doesn't exist), such validation is responsibility
-of the transformation function if required.
-
-Example transformation module `transform.js` with exported function called transform:
-
-```js
-module.exports = {
-    render: (path) => {
-        /*
-        Some transformation happens in here and it's result which is
-        a string is assigned to result variable which is returned.
-        */
-        return result;
-    }
-}
-```
-
-#### Removal operations
-
-Any file/directory prefixed by `!` will be removed from the destination based on it's full path
-relative from `ops` execution directory to source file/directory path.
-
 ## `ops version <type>`
 
 creates everything necessary for the new release
@@ -741,15 +531,15 @@ EXAMPLES
 - _new-version_ allows setting own version regardles of VERSION file. **Incrementing NPM version separately is not supported in this case. NPM packages are also bumped to specified version.**
 
 > Prerelease Note: Prerelease should only be user in **master** branch.
-
+\\
 > Patch Note: Patch is used on **release/x.x** branches for creating patch releases
 > When creating new **release/x.x** branch 2 steps are needed:
 >
 > - creating _patch_ version on **release/x.x** branch
 > - creating _preminor_ or _premajor_ version on **master** branch
-
+\\
 > Dependencies for packages are updated on all package.json files. If prerelease version in specified full version is specified (example: 4.0.0-201911.0), or if non prerelease version ends with x (example: 3.5.x)
-
+\\
 > NPM packages node: For npm package to update properly _wsrun-version_ preset needs to be in _scripts_ portion of _package.json_. (example: `"wsrun-version": "yarn wsrun -p @adinsure-tools/* -p @adinsure/* -c"`)
 
 ## `ops sql <type> <module> [flags]`
@@ -771,7 +561,7 @@ OPTIONS
   -o, --offline                  generate database script with timestamp
   -v, --version=version          version for which you're generating database script
 
-// when using the Extend datascript type to add a new column (column-name, column-type) to the table (table-name in table-schema) 
+Extend type options for extending DBs:
   --table-schema                 table schema name
   --table-name                   table name
   --column-name                  new column's name 

package/bin/dev.cmd

@@ -0,0 +1,3 @@
+@echo off
+
+node --loader ts-node/esm --trace-warnings "%~dp0\dev.js" %*

package/bin/dev.js

@@ -0,0 +1,6 @@
+#!/usr/bin/env ts-node
+// eslint-disable-next-line node/shebang, unicorn/prefer-top-level-await
+(async () => {
+    const oclif = await import('@oclif/core');
+    await oclif.execute({ type: 'esm', development: true, dir: import.meta.url });
+})();

package/bin/run.cmd

@@ -1,3 +1,3 @@
 @echo off
 
-node "%~dp0\run" %*
+ts-node-esm "%~dp0\run.js" %*

package/bin/run.js

@@ -0,0 +1,8 @@
+#!/usr/bin/env node
+// eslint-disable-next-line node/shebang
+import oclif from '@oclif/core';
+
+/* eslint-disable unicorn/prefer-top-level-await */
+oclif.run(process.argv.slice(2), import.meta.url)
+    .then(oclif.flush)
+    .catch(oclif.Errors.handle);

package/lib/command.base.d.ts

@@ -1,17 +1,21 @@
-import { Command } from '@oclif/command';
-import { IConfig } from '@oclif/config';
-import SecurityContext from './security/context';
-export default abstract class CommandBase extends Command {
+import { Command, Config } from '@oclif/core';
+import SecurityContext from './security/context.js';
+export default abstract class CommandBase<T extends typeof Command> extends Command {
     protected readonly security: SecurityContext;
-    constructor(argv: string[], config: IConfig);
+    constructor(argv: string[], config: Config);
     getGitRoot(startDir?: string): Promise<string>;
     getVersion(versionFile?: string, ...filesToCheck: string[]): Promise<string>;
     /**
      * Resolve path to Changelog folder from current execution directory
+     * @returns {string} the resolved path to changelogs
      */
     getChangelogsRoot(): Promise<string>;
     /**
      * Get all files inside directory and normalize it against {baseRelativePath}.
+     * @param {string} dir The name or path of the current directory
+     * @param {string} baseRelativePath The relatice path format from the `dir`
+     * @param {RegExp} filter Regular expressions filter for the file path
+     * @returns {string[]} An array of files inside the directory with the specified filter
      */
     getFilesRecursive(dir: string, baseRelativePath: string, filter: RegExp): Promise<string[]>;
 }

package/lib/command.base.jira.d.ts

@@ -1,11 +1,10 @@
-import { flags } from '@oclif/command';
-import JiraApi = require('jira-client');
-import CommandBase from './command.base';
-export default abstract class CommandBaseJira extends CommandBase {
+import JiraApi from 'jira-client';
+import CommandBase from './command.base.js';
+export default abstract class CommandBaseJira extends CommandBase<typeof CommandBaseJira> {
     static flags: {
-        username: flags.IOptionFlag<string>;
-        password: flags.IOptionFlag<string>;
-        hostname: flags.IOptionFlag<string>;
+        username: import("@oclif/core/lib/interfaces/parser.js").OptionFlag<string, import("@oclif/core/lib/interfaces/parser.js").CustomOptions>;
+        password: import("@oclif/core/lib/interfaces/parser.js").OptionFlag<string, import("@oclif/core/lib/interfaces/parser.js").CustomOptions>;
+        hostname: import("@oclif/core/lib/interfaces/parser.js").OptionFlag<string, import("@oclif/core/lib/interfaces/parser.js").CustomOptions>;
     };
-    jiraInit(url: string, username: string, password: string): Promise<JiraApi>;
+    jiraInit(urlString: string, username: string, password: string): Promise<JiraApi>;
 }

package/lib/command.base.jira.js

@@ -1,37 +1,39 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-const command_1 = require("@oclif/command");
-const JiraApi = require("jira-client");
-const command_base_1 = require("./command.base");
-class CommandBaseJira extends command_base_1.default {
-    async jiraInit(url, username, password) {
-        const jiraUrl = new URL(url);
-        const jira = new JiraApi({
-            protocol: jiraUrl.protocol,
-            host: jiraUrl.hostname,
-            username,
-            password,
-            apiVersion: '2',
-            strictSSL: true
+import { __awaiter } from "tslib";
+import { Flags } from '@oclif/core';
+import JiraApi from 'jira-client';
+import url from 'url';
+import CommandBase from './command.base.js';
+class CommandBaseJira extends CommandBase {
+    jiraInit(urlString, username, password) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const jiraUrl = new url.URL(urlString);
+            const jira = new JiraApi({
+                protocol: jiraUrl.protocol,
+                host: jiraUrl.hostname,
+                username,
+                password,
+                apiVersion: '2',
+                strictSSL: true,
+            });
+            return jira;
         });
-        return jira;
     }
 }
-exports.default = CommandBaseJira;
 CommandBaseJira.flags = {
-    username: command_1.flags.string({
+    username: Flags.string({
         description: 'jira username',
         env: 'JIRA_USERNAME',
-        required: true
+        required: true,
     }),
-    password: command_1.flags.string({
+    password: Flags.string({
         description: 'jira password',
         env: 'JIRA_PASSWORD',
-        required: true
+        required: true,
     }),
-    hostname: command_1.flags.string({
+    hostname: Flags.string({
         description: 'jira hostname',
         default: 'https://jira.adacta-fintech.com',
-        env: 'JIRA_HOSTNAME'
-    })
+        env: 'JIRA_HOSTNAME',
+    }),
 };
+export default CommandBaseJira;