APIOps Toolkit for Azure APIM v7.0.0-alpha.2.0.0

Added

• Added unit tests for the extractor and publisher.
• We now support a dry-run option for the publisher (#754). It will process files normally but not make any changes to APIM. This is useful for validating configurations and previewing changes before executing them. This is disabled by default, but you can control this by:
  • Setting the DRY_RUN configuration value to true | false
  • Passing --dry-run to the publisher executable. This naked flag enables dry run mode.
  • Passing --dry-run true|false to the publisher executable.
• The publisher now attempts to validate resource state before making changes to APIM. This reduces the chances of failing mid-run because of an issue that could have been caught earlier. Specifically, it checks that:
  • Resources don't have cyclical relationships (e.g. subscription A depends on group B which depends on API C which depends on subscription A). This shouldn't happen if teams rely on the extractor, but code-first deployments or editing the extracted JSON incorrectly can cause this.
  • Resources aren't missing predecessors. For example, let's say we put policy A that uses named value B. The publisher will check whether named value B is also in source control. If the predecessor is missing:
    • If the configuration STRICT_VALIDATION is set to true, then the publisher will throw an error.
    • Otherwise, the publisher will log a warning saying that the named value was not found in source. This allows for scenarios where different teams manage different resources (maybe another team is responsible for managing named values).

Fixed

• Fixed a bug when publishing workspace API revisions

Full Changelog: v7.0.0-alpha.1.0.4...v7.0.0-alpha.2.0.0