Red Hat Satellite 6.3 adds the ability to create subscriptions that only become active after a specified date. A procedure on how to configure such subscriptions and some context as to why this would be useful must be added to the documentation.
Assigning to Stephen for review. Stephen - I suspect we'll need to raise one or two more RFEs for this topic in addition to this one. For example, one to add some conceptual content to the Architecture Guide, and possibly another to update any search or filter options to include this new option. At a glance, the content in *this* bug looks like it might be a good candidate for the Managing Subscriptions chapter of the Content Management Guide. What do you think?
(In reply to Andrew Dahms from comment #2) > Assigning to Stephen for review. > > Stephen - I suspect we'll need to raise one or two more RFEs for this topic > in addition to this one. For example, one to add some conceptual content to > the Architecture Guide, and possibly another to update any search or filter > options to include this new option. > > At a glance, the content in *this* bug looks like it might be a good > candidate for the Managing Subscriptions chapter of the Content Management > Guide. > > What do you think? The chapter "Managing Subscriptions"[1] seems the only place in the Content Management Guide. In the Architecture Guide, in the section "Adding Satellite Subscription Manifests to Satellite Server", there is a link to the "Managing Subscriptions"[1]chapter mentioned above. We could add a para to say "Future dated subscriptions can be added to the subscription manifest to enable you to ensure uninterrupted content updates." [1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/managing_subscriptions
Hi Stephen, I have now added two bugs to the 'Depends On' field that serve as engineering trackers for this feature. Shall I create a second bug for the conceptual work? Kind regards, Andrew
(In reply to Andrew Dahms from comment #5) > Hi Stephen, > > I have now added two bugs to the 'Depends On' field that serve as > engineering trackers for this feature. Thank you > > Shall I create a second bug for the conceptual work? > I can clone this bug now for the Arch Guide
Shea Deantonio can help with that.
Updating the target milestone to reflect the time frame in which this work was completed.