@esm-js/jira.js/src/agile/featureFlags.ts

A comprehensive JavaScript/TypeScript library designed for both Node.JS and browsers, facilitating seamless interaction with the Atlassian Jira API.

import type * as Models from './models';
import type * as Parameters from './parameters';
import type { Client } from '../clients';
import type { Callback } from '../callback';
import type { RequestConfig } from '../requestConfig';

export class FeatureFlags {
  constructor(private client: Client) {}

  /**
   * Update / insert Feature Flag data.
   *
   * Feature Flags are identified by their ID, and existing Feature Flag data for the same ID will be replaced if it
   * exists and the updateSequenceId of existing data is less than the incoming data.
   *
   * Submissions are performed asynchronously. Submitted data will eventually be available in Jira; most updates are
   * available within a short period of time, but may take some time during peak load and/or maintenance times. The
   * getFeatureFlagById operation can be used to confirm that data has been stored successfully (if needed).
   *
   * In the case of multiple Feature Flags being submitted in one request, each is validated individually prior to
   * submission. Details of which Feature Flags failed submission (if any) are available in the response object.
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'WRITE' scope for Connect apps.
   */
  async submitFeatureFlags<T = Models.SubmitFeatureFlags>(
    parameters: Parameters.SubmitFeatureFlags,
    callback: Callback<T>,
  ): Promise<void>;
  /**
   * Update / insert Feature Flag data.
   *
   * Feature Flags are identified by their ID, and existing Feature Flag data for the same ID will be replaced if it
   * exists and the updateSequenceId of existing data is less than the incoming data.
   *
   * Submissions are performed asynchronously. Submitted data will eventually be available in Jira; most updates are
   * available within a short period of time, but may take some time during peak load and/or maintenance times. The
   * getFeatureFlagById operation can be used to confirm that data has been stored successfully (if needed).
   *
   * In the case of multiple Feature Flags being submitted in one request, each is validated individually prior to
   * submission. Details of which Feature Flags failed submission (if any) are available in the response object.
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'WRITE' scope for Connect apps.
   */
  async submitFeatureFlags<T = Models.SubmitFeatureFlags>(
    parameters: Parameters.SubmitFeatureFlags,
    callback?: never,
  ): Promise<T>;
  async submitFeatureFlags<T = Models.SubmitFeatureFlags>(
    parameters: Parameters.SubmitFeatureFlags,
    callback?: Callback<T>,
  ): Promise<void | T> {
    const config: RequestConfig = {
      url: '/rest/featureflags/0.1/bulk',
      method: 'POST',
      data: {
        properties: parameters.properties,
        flags: parameters.flags,
        providerMetadata: parameters.providerMetadata,
      },
    };

    return this.client.sendRequest(config, callback);
  }

  /**
   * Bulk delete all Feature Flags that match the given request.
   *
   * One or more query params must be supplied to specify Properties to delete by. Optional param `_updateSequenceId` is
   * no longer supported. If more than one Property is provided, data will be deleted that matches ALL of the Properties
   * (e.g. treated as an AND). See the documentation for the submitFeatureFlags operation for more details.
   *
   * E.g. DELETE /bulkByProperties?accountId=account-123&createdBy=user-456
   *
   * Deletion is performed asynchronously. The getFeatureFlagById operation can be used to confirm that data has been
   * deleted successfully (if needed).
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'DELETE' scope for Connect apps.
   */
  async deleteFeatureFlagsByProperty<T = unknown>(
    parameters: Parameters.DeleteFeatureFlagsByProperty,
    callback: Callback<T>,
  ): Promise<void>;
  /**
   * Bulk delete all Feature Flags that match the given request.
   *
   * One or more query params must be supplied to specify Properties to delete by. Optional param `_updateSequenceId` is
   * no longer supported. If more than one Property is provided, data will be deleted that matches ALL of the Properties
   * (e.g. treated as an AND). See the documentation for the submitFeatureFlags operation for more details.
   *
   * E.g. DELETE /bulkByProperties?accountId=account-123&createdBy=user-456
   *
   * Deletion is performed asynchronously. The getFeatureFlagById operation can be used to confirm that data has been
   * deleted successfully (if needed).
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'DELETE' scope for Connect apps.
   */
  async deleteFeatureFlagsByProperty<T = unknown>(
    parameters: Parameters.DeleteFeatureFlagsByProperty,
    callback?: never,
  ): Promise<T>;
  async deleteFeatureFlagsByProperty<T = unknown>(
    parameters: Parameters.DeleteFeatureFlagsByProperty,
    callback?: Callback<T>,
  ): Promise<void | T> {
    const config: RequestConfig = {
      url: '/rest/featureflags/0.1/bulkByProperties',
      method: 'DELETE',
      params: {
        _updateSequenceId: parameters.updateSequenceId,
      },
    };

    return this.client.sendRequest(config, callback);
  }

  /**
   * Retrieve the currently stored Feature Flag data for the given ID.
   *
   * The result will be what is currently stored, ignoring any pending updates or deletes.
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'READ' scope for Connect apps.
   */
  async getFeatureFlagById<T = Models.GetFeatureFlagById>(
    parameters: Parameters.GetFeatureFlagById,
    callback: Callback<T>,
  ): Promise<void>;
  /**
   * Retrieve the currently stored Feature Flag data for the given ID.
   *
   * The result will be what is currently stored, ignoring any pending updates or deletes.
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'READ' scope for Connect apps.
   */
  async getFeatureFlagById<T = Models.GetFeatureFlagById>(
    parameters: Parameters.GetFeatureFlagById,
    callback?: never,
  ): Promise<T>;
  async getFeatureFlagById<T = Models.GetFeatureFlagById>(
    parameters: Parameters.GetFeatureFlagById,
    callback?: Callback<T>,
  ): Promise<void | T> {
    const config: RequestConfig = {
      url: `/rest/featureflags/0.1/flag/${parameters.featureFlagId}`,
      method: 'GET',
    };

    return this.client.sendRequest(config, callback);
  }

  /**
   * Delete the Feature Flag data currently stored for the given ID.
   *
   * Deletion is performed asynchronously. The getFeatureFlagById operation can be used to confirm that data has been
   * deleted successfully (if needed).
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'DELETE' scope for Connect apps.
   */
  async deleteFeatureFlagById<T = unknown>(
    parameters: Parameters.DeleteFeatureFlagById,
    callback: Callback<T>,
  ): Promise<void>;
  /**
   * Delete the Feature Flag data currently stored for the given ID.
   *
   * Deletion is performed asynchronously. The getFeatureFlagById operation can be used to confirm that data has been
   * deleted successfully (if needed).
   *
   * Only Connect apps that define the `jiraFeatureFlagInfoProvider` module can access this resource. This resource
   * requires the 'DELETE' scope for Connect apps.
   */
  async deleteFeatureFlagById<T = unknown>(parameters: Parameters.DeleteFeatureFlagById, callback?: never): Promise<T>;
  async deleteFeatureFlagById<T = unknown>(
    parameters: Parameters.DeleteFeatureFlagById,
    callback?: Callback<T>,
  ): Promise<void | T> {
    const config: RequestConfig = {
      url: `/rest/featureflags/0.1/flag/${parameters.featureFlagId}`,
      method: 'DELETE',
      params: {
        _updateSequenceId: parameters.updateSequenceId,
      },
    };

    return this.client.sendRequest(config, callback);
  }
}