- Release Notes
- Introduction
- Governance
- Source Control
- CI/CD Pipelines
- Feeds Management
- Logging
Custom Feeds
You can set up your own feeds, and then add them in Automation Ops as custom package or library feeds to manage the packages and versions they contain, and deploy them to Orchestrator tenants.
- In Automation Cloud™ , navigate to Automation Ops from the left-side navigation bar.
- Select Manage Feeds > Custom.
A table listing the name, URL, and type of existing custom feeds is displayed on the page. You can refresh the data by clicking Refresh above the table. A refresh is triggered automatically every 15 minutes and you are prompted to reload the data.
You can manage your custom feeds as follows:
- Add a new feed by clicking Add Feed above the table.
- Manage an existing feed by selecting it in the table.
-
Delete a feed by hovering over the right side of its entry, and then clicking Delete.
- In Automation Cloud™ , navigate to Automation Ops from the left-side navigation bar.
- Select Manage Feeds > Custom.
- In the list of feeds, select a feed.
On the Packages tab, a list of packages added to the feed is displayed on the page. The following information is displayed for each one: name, description, latest version, and up to three package tags.
To filter the list of packages, use the boxes above the table to search by name or filter by one or more package tags. You can refresh the data by clicking Refresh above the table.
For information on how you can manage the packages, see:
Add a New Package
Add a New Version to an Existing Package
Copy a Package Version to Another Feed
You can copy any package version from a feed to another Orchestrator feed or custom feed.
Delete a Package Version
You can remove package versions that are no longer needed. Before you remove a version, make sure no processes are using the version.
View Package Version Details
On the Deployment tab, a list of feed deployments is displayed on the page.
Deploy a Feed to a Tenant
You can deploy a custom feed to one or more tenants. Each tenant can only have one feed for packages and one for libraries.
When deploying a custom feed to a tenant:
- The type of the custom feed must match the type of the tenant feed (packages to packages, libraries to libraries).
- Any packages from the previously assigned package feed that are in use in the tenant become unavailable after you deploy the custom feed if they are not also included in the custom feed.
-
The Orchestrator deployment settings for the tenant are updated as follows:
-
For a package feed:
- The External deployment setting is selected.
- The API Key security setting is selected and the optional key is added.
-
For a library feed:
- The External deployment setting is selected.
- The API Key security settings is selected and the optional key is added.
- The Both host and tenant feeds setting is selected.
-
Remove a Feed Deployment
- Select the Deployment tab.
- In the list of tenants, hover over the right side of the feed deployment you want to remove, and then click Delete.
- A confirmation dialog is displayed. Click Remove to confirm.
The feed used by the tenant after the custom feed is removed is determined as follows:
- For a library feed, the host feed is selected for the tenant.
- For a package feed, the Internal deployment option is selected for the tenant.