Managing Content Views

In the orcharhino management UI, navigate to Content > Content Views and click Create content view.

In the Name field, enter a name for the view. orcharhino automatically completes the Label field from the name you enter.

In the Description field, enter a description of the view.

In the Type field, select a Content view or a Composite content view.

Optional: If you want to solve dependencies automatically every time you publish this Content View, select the Solve dependencies checkbox. Dependency solving slows the publishing time and might ignore any Content View filters you use. This can also cause errors when resolving dependencies for errata.

Optional: If you want to designate this Content View for importing from an upstream server, select the Import only checkbox. Import-only content views cannot be published directly.

Click Create content view.

Click Create content view to create the Content View.

In the Repositories tab, select the repository from the Type list that you want to add to your Content View, select the checkbox next to the available repositories you want to add, then click Add repositories.

Click Publish new version and in the Description field, enter information about the version to log changes.

Optional: You can enable a promotion path by clicking Promote to Select a lifecycle environment from the available promotion paths to promote new version.

Click Next.

On the Review page, you can review the environments you are trying to publish.

Click Finish.

Obtain a list of repository IDs:

$ hammer repository list --organization "My_Organization"

Create the Content View and add repositories:

$ hammer content-view create \
--description "My_Content_View" \
--name "My_Content_View" \
--organization "My_Organization" \
--repository-ids 1,2

Publish the view:

$ hammer content-view publish \
--description "My_Content_View" \
--name "My_Content_View" \
--organization "My_Organization"

Optional: To add a repository to an existing Content View, enter the following command:

# hammer content-view add-repository \
--name "My_Content_View" \
--organization "My_Organization" \
--repository-id repository_ID

In the orcharhino management UI, navigate to a published version of a Content View > Module Streams to view the module streams that are available for the Content Types.

Use the Search field to search for specific modules.

To view the information about the module, click the module and its corresponding tabs to include Details, Repositories, Profiles, and Artifacts.

List all organizations:

$ hammer organization list

View all module streams for your organization:

$ hammer module-stream list \
--organization-id My_Organization_ID

promote_or_remove_content_views

promote_or_remove_content_views_to_environment.

In the orcharhino management UI, navigate to Content > Content Views and select the Content View that you want to promote.

Select the version that you want to promote, click the vertical ellipsis icon, and click Promote.

Select the environment where you want to promote the Content View and click Promote.

To promote a selected Content View version from Library across all life cycle environments within an organization, run the following Bash script:

ORG="My_Organization"
CVV_ID=3

for i in $(hammer --no-headers --csv lifecycle-environment list --organization $ORG | awk -F, {'print $1'} | sort -n)
do
   hammer content-view version promote --organization $ORG --to-lifecycle-environment-id $i --id $CVV_ID
done

Display information about your Content View version to verify that it is promoted to the required lifecycle environments:

# hammer content-view version info --id 3

In the orcharhino management UI, navigate to Content > Content Views and click Create content view.

In the Create content view window, enter a name for the view in the Name field. orcharhino automatically completes the Label field from the name you enter.

Optional: In the Description field, enter a description of the view.

On the Type tab, select Composite content view.

Optional: If you want to automatically publish a new version of the Composite Content View when a Content View is republished, select the Auto publish checkbox.

Click Create content view.

On the Content views tab, select the Content Views that you want to add to the Composite Content View, and then click Add content views.

In the Add content views window, select the version of each Content View.

Optional: If you want to automatically update the Content View to the latest version, select the Always update to latest version checkbox.

Click Add, then click Publish new version.

Optional: In the Description field, enter a description of the Content View.

In the Publish window, set the Promote switch, then select the lifecycle environment.

Click Next, then click Finish.

Before you create the Composite Content Views, list the version IDs for your existing Content Views:

$ hammer content-view version list \
--organization "My_Organization"

Create a new Composite Content View. When the --auto-publish option is set to yes, the Composite Content View is automatically republished when a Content View it includes is republished:

$ hammer content-view create \
--composite \
--auto-publish yes \
--name "Example_Composite_Content_View" \
--description "Example Composite Content View" \
--organization "My_Organization"

Add a Content View to the Composite Content View. You must include the Content View Version ID and use the --latest option. To add multiple Content Views to the Composite Content View, repeat this step for every Content View you want to include:

$ hammer content-view component add \
--component-content-view-id Content_View_Version_ID \
--latest \
--composite-content-view "Example_Composite_Content_View"

Publish the Composite Content View:

$ hammer content-view publish \
--name "Example_Composite_Content_View" \
--description "Initial version of Composite Content View" \
--organization "My_Organization"

Promote the Composite Content View across all environments:

$ hammer content-view version promote \
--content-view "Example_Composite_Content_View" \
--version 1 \
--to-lifecycle-environment "Development" \
--organization "My_Organization"
$ hammer content-view version promote \
--content-view "Example_Composite_Content_View" \
--version 1 \
--to-lifecycle-environment "Testing" \
--organization "My_Organization"
$ hammer content-view version promote \
--content-view "Example_Composite_Content_View" \
--version 1 \
--to-lifecycle-environment "Production" \
--organization "My_Organization"

In the orcharhino management UI, navigate to Content > Content Views and select a Content View.

On the Filters tab, click Create filter.

Enter a name.

From the Content type list, select a content type.

From the Inclusion Type list, select either Include filter or Exclude filter.

Optional: In the Description field, enter a description for the filter.

Click Create filter to create your content filter.

Depending on what you enter for Content Type, add rules to create the filter that you want.

Select if you want the filter to Apply to subset of repositories or Apply to all repositories.

Click Publish New Version to publish the filtered repository.

Optional: In the Description field, enter a description of the changes.

Click Create filter to publish a new version of the Content View.

Add a filter to the Content View. Use the --inclusion false option to set the filter to an Exclude filter:

$ hammer content-view filter create \
--name "Errata Filter" \
--type erratum --content-view "Example_Content_View" \
--description "My latest filter" \
--inclusion false \
--organization "My_Organization"

Add a rule to the filter:

$ hammer content-view filter rule create \
--content-view "Example_Content_View" \
--content-view-filter "Errata Filter" \
--start-date "YYYY-MM-DD" \
--types enhancement,bugfix \
--date-type updated \
--organization "My_Organization"

Publish the Content View:

$ hammer content-view publish \
--name "Example_Content_View" \
--description "Adding errata filter" \
--organization "My_Organization"

Promote the view across all environments:

$ hammer content-view version promote \
--content-view "Example_Content_View" \
--version 1 \
--to-lifecycle-environment "Development" \
--organization "My_Organization"
$ hammer content-view version promote \
--content-view "Example_Content_View" \
--version 1 \
--to-lifecycle-environment "Testing" \
--organization "My_Organization"
$ hammer content-view version promote \
--content-view "Example_Content_View" \
--version 1 \
--to-lifecycle-environment "Production" \
--organization "My_Organization"