Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A library is collection of resources. Libraries or solution kits can be added to an API as a requirement. From this point on, when migrating this API, AAGM checks if the requirements are also present on the target.

Here you can see how to create a new library and add it to an API as a requirement.

https://apiida.atlassian.net/wiki/spaces/AAGM/pages/7654572033/Working+with+git#But-my-API-needs-for-example-a-cluster-propery.-What-now%3F-Libraries!

Contents

The contents of the library or solution kit are listed here.

...

Version Control

...

Version Control (Library only)

Here the content can be updated from the git or also from the node.

...

Update an existing Library

Select "Select from node and push to git" here. You will be redirected to the overview of the resources of the gateway from which the library was created.
You can also select a different gateway. But, some content may not be found and then you will have to select it manually. After you have made the needed changes to the content, click "Update Library".

Info

If you only want to update the contents of the library itself, follow the steps described. But first you should update the resources of the corresponding node. Resources -> Reload Resources

Migration, Variables, Requirements (Library only)

These functions behave as in Group of APIs - Folder.
A library should be migrated like an API. When migrating an API that requires it, a check is made to see if it exists on the target.

It also checks if the library would need to be updated on the target.

...