Release v3.0.7

Fix: Resolved a false positive error log that was incorrectly triggered during a catalog upload when using an organization key.

Full Changelog: [GitHub Compare: 3.0.6 → 3.0.7](3.0.6...3.0.7)

Release v3.0.6

QuickFix: An internal temporary workaround does a volatile upload even when performing a registration upload, which can fail with the new organization keys. This quick-fix forces this workaround to stop causing the tool fail completely.

Release v3.0.5

Fix: Volatile Uploads should never look for manifest files. This has been removed.
NF: Preparing this tool for Volatile Connector Upload support.

What's Changed

• Bump MSTest from 3.6.4 to 3.7.0 by @dependabot in #60
• Bump MSTest from 3.7.0 to 3.7.2 by @dependabot in #67
• Bump coverlet.collector from 6.0.2 to 6.0.4 by @dependabot in #65
• Bump YamlDotNet from 16.2.1 to 16.3.0 by @dependabot in #61
• Bump FluentAssertions from 7.0.0 to 7.1.0 by @dependabot in #68
• Support connectors & fix for volatile upload by @janstaelensskyline in #73

Full Changelog: 3.0.4...3.0.5

Release 3.0.4

Catalog Support for Different Types

The catalog now supports different catalog types, this tooling is updated to reflect this enhancement.

When uploading a new version, unless explicitly defined in a catalog.yml file, the artifact type is automatically determined based on the type of artifact being uploaded. The following changes have been made to the catalog types:

• automationscript → Automation
• connector → Connector
• solution → Custom Solution
• chatopsextension → ChatOps Extension
• dashboard → Dashboard
• adhocdatasource → Ad Hoc Data Source
• datatransformer → Data Transformer
• scriptedconnector → Scripted Connector
• userdefinedapi → User-Defined API
• visio → Visual Overview

---

What's Changed

• Updated existing catalog types to support new naming conventions and functionality.
  By @janstaelensskyline in [#59](#59)

Full Changelog: [Compare v3.0.3...v3.0.4](3.0.3...3.0.4)

Release v3.0.3

Added debug logging

Full Changelog: 3.0.2...3.0.3

Release v3.0.2

What's Changed

• Bump the mstest group with 2 updates by @dependabot in #49
• Bump FluentAssertions from 6.12.1 to 6.12.2 by @dependabot in #47
• Bump YamlDotNet from 16.1.3 to 16.2.1 by @dependabot in #48, #54
• Fix issue with serialization of manifest.yml file by @MichielOda in #58

Full Changelog: 3.0.1...3.0.2

Release v3.0.1

Breaking Change for with-registration Subcommand

The with-registration subcommand no longer uses the uri-sourcecode to identify the catalog item. It now requires the 'catalog-identifier', as displayed on the catalog UI. The GUID must be provided either via an argument or through the use of a catalog.yml/manifest.yml file, as detailed in the DataMiner documentation.

New Features

• Support for using catalog.yml or manifest.yml to provide additional metadata for the catalog UI.
• Added support for using README.md and images to enhance the catalog UI.
• Allows updating only the catalog UI metadata without the need to register a new version of the artifact.
• Allows uploads for all Catalog Item types, including Connectors.

What's Changed

• Bump Serilog.Sinks.Console from 5.0.1 to 6.0.0 by @dependabot in #35
• Bump Moq from 4.20.70 to 4.20.72 by @dependabot in #39
• Bump FluentAssertions from 6.12.0 to 6.12.1 by @dependabot in #40
• Dev/support all types by @janstaelensskyline in #41
• Bump Extensions.Logging.Mock and Moq by @dependabot in #46
• Bump the mstest group with 2 updates by @dependabot in #45

Full Changelog: 2.0.2...3.0.1

prerelease v3.0.1-beta8

Release Notes

New Update: Catalog Upload Enhancements and Deployment Workaround

Highlights:

• Deployment Support Update: Deployments initiated from the catalog through API calls are now unsupported for uploads using the new API.
• Internal Workaround Implemented: To ensure continued deployment capability, a workaround has been added. This involves returning the deployment-capable key from a secondary, volatile upload process during catalog uploads with registration (with-registration).

Details:

• The deployment process now automatically triggers a secondary upload to generate the necessary key for deployments, ensuring that the catalog upload remains functional for deployment purposes.
• This change maintains deployment compatibility while using the new API structure for catalog operations.

prerelease v3.0.1-beta7

New catalog API returns different json structure. Adjusted the code to parse this correctly.

prerelease v3.0.1-beta6

Fixed an issue where the new registration did not return the catalog identifier of a new version.