When a custom resource is in use, we attempt to do an update after a failed deletion (default behavior as we want to recreate it).
This used to fail since the exception was not caught and was also burried inside of another exception.
The exception is now caught and the update is attempted.
The cheatsheet documents contained similar error:
[ERROR] version: '3.1.1-SNAPSHOT': Plugin com.vmware.pscoe.maven.plugins:abx-package-maven-plugin:3.1.1-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact
The cheatsheet documents are properly generated.
An exception was thrown like: The request was rejected because the URL contained a potentially malicious String "//"","path":"/blueprint/api/blueprints/b355c354-a4b6-4d55-800a-8b4232f29b83/versions/2024-12-06-18-34-42//actions/unrelease
This was because of the // after the version id.
The extra / is removed when forming the url now
We were getting an error when trying to package ABX project:
[ERROR] Failed to execute goal com.vmware.pscoe.maven.plugins:abx-package-maven-plugin:2.44.0:package (default-package) on project anothertest: Error creating ABX bundle: duplicate entry: node_modules/run-script-os/index.js -> [Help 1]
The ABX package created successfully.
ABX packages are ignored in the bundle. The Installer completes the task without installing the packages.
The Installer asks the user whether to install ABX packages and in case of positive response installs the packages.
The default value was Y which often results in the user having to provide explicitly N as value.
In interactive mode, it is assumed that the Java Installer is run manually by a user. In that case if the user wants to run a workflow it is more common to login into the Aria Automation Orchestrator UI and run the workflow from there benefiting from all of the tracking and monitoring offered by Aria Automation Orchestrator.
The default value is set to N enabling the user to just proceed to the next option without providing explicit value for the most common use cases.
There was a (Y/N) hardcoded in the question which resulted in double entry:
Is single tenant environment (Y/N)? (Y/N) [Y]:
The question is updated:
Is single tenant environment? (Y/N) [Y]:
This is just an internal restructuring effort, no functionality was changed.
This is just an internal restructuring effort, no functionality was changed.
This is just an internal restructuring effort, no functionality was changed.
This is just an internal restructuring effort, no functionality was changed.
The package name and version of the type definitions are being installed dynamically based on the configuration of the solution.
This ensures the type definitions available for type hinting / autocomplete in the IDE and for the transpilation are matching the actual code definitions of the unit test framework.
The type definitions installed were always the same package and version - the BTVA built-in Jasmine definitions (link is to v3.1.1, might be outdated at later point in time).
The configuration in the pom file affects both the framework being used and its type definitions being made available.