Capsule Lifecycle Environments

Hello,

I use composite content views which point to content view versions that are only promoted to the "Library" environment. My composite view versions are then promoted through the remaining environments in the lifecycle. My question is, on my Capsule(s), do I have to sync the "Library" environment since my composite views reference versions that are only in "Library" or can I omit the "Library" and content which is referenced will automagically get synced?

Regards,

j

Hey Jason,

When you promote a composite content view to a lifecycle environment that
has a capsule associated with it, all of the content in the content view
versions associated with that composite content view will be available. In
short, your content views should be fine in Library as long as the
composite content view versions are promoted to the right lifecycle env.

-John

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

··· On Tue, Mar 28, 2017 at 11:48 AM, 'Jason B. Nance' via Foreman users < foreman-users@googlegroups.com> wrote:

Hello,

I use composite content views which point to content view versions that
are only promoted to the “Library” environment. My composite view versions
are then promoted through the remaining environments in the lifecycle. My
question is, on my Capsule(s), do I have to sync the “Library” environment
since my composite views reference versions that are only in “Library” or
can I omit the “Library” and content which is referenced will automagically
get synced?

Regards,

j


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.