Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs for rolling content views #3518

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions guides/common/assembly_managing-content-views.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,10 @@ include::modules/proc_viewing-module-streams.adoc[leveloffset=+1]

include::modules/proc_promoting-a-content-view.adoc[leveloffset=+1]

include::modules/con_rolling-content-views.adoc[leveloffset=+1]

include::modules/proc_creating-a-rolling-content-view.adoc[leveloffset=+1]

include::modules/con_composite-content-views-overview.adoc[leveloffset=+1]

include::modules/proc_creating-a-composite-content-view.adoc[leveloffset=+1]
Expand Down
9 changes: 9 additions & 0 deletions guides/common/modules/con_rolling-content-views.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
[id="rolling-content-views"]
= Rolling content views

A rolling content view is a curated subset of content that your hosts can access.
It is a subset of the Library environment and contains the latest synchronized content from one or multiple repositories.
You can use a rolling content view to provide a continuous stream of synchronized content to hosts.

When you synchronize repositories to {Project}, all rolling content views that contain them get automatically updated to include the latest changes.
You do not have to publish and/or promote a rolling content view compared to content views or composite content views.
44 changes: 44 additions & 0 deletions guides/common/modules/proc_creating-a-rolling-content-view.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
[id="creating-a-rolling-content-view"]
= Creating a rolling content view

Use this procedure to create a rolling content view.
To use the CLI instead of the {ProjectWebUI}, see the xref:cli-creating-a-rolling-content-view[].

.Procedure
. In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
. Click *Create content view*.
. In the *Create content view* window, enter a name for the content view in the *Name* field.
{Project} automatically completes the *Label* field from the name you enter.
. Optional: In the *Description* field, enter a description of the content view.
. On the *Type* tab, select *Rolling content view*.
. Click *Create content view*.
. Click *Show repositories*.
. Select the repositories that you want to add to your rolling content view.
. Click *Add repositories* to add all selected repositories to your rolling content view.

[id="cli-creating-a-rolling-content-view"]
.CLI procedure
. Before you create a rolling content views, list all available repositories:
+
[options="nowrap" subs="+quotes"]
----
$ hammer repository list \
--fields id,name,product \
--organization "_My_Organization_"
----
. Create your rolling content view:
+
[options="nowrap" subs="+quotes"]
----
$ hammer content-view create \
--name "_My_Rolling_Content_View_" \
--organization "_My_Organization_" \
--repository-ids _My_List_Of_Repository_IDs_ \
--rolling
----

.Next steps
* You cannot publish or promote your rolling content view.
Instead, continue by adding it to your activation key.
For more information, see xref:Creating_an_Activation_Key_{context}[].
* To register a host to your rolling content view, see {ManagingHostsDocURL}registering-a-host_managing-hosts[Registering a host] in _{ManagingHostsDocTitle}_.