We decided not to export subscriptions for blueprints. We believe that this is a sensible approach to prevent users from sharing sensitive data. That might happen if we exported Subscription and users shared the blueprint afterwards.

However, when doing that, an important information is lost - whether or not the blueprint was subscribed. In both cases, there will be no field for Subscription. We might want to be able to tell if the blueprint was subscribed or not, if it is imported again.

Goal: 

• Figure out how to handle Subscription in the Import Wizard
  • Either prefill the default or leave it empty.
•  Options:
  • We can figure out a way to tell if the exported blueprint had a subscription or not.
  • That way, we will be able to either prefill a default subscription on import or uncheck the subscription in the Wizard on import.
  • If we are doing this, we might want to make sure that it is intuitive for users who try to modify the Blueprint.
  • Unclear: How is this for on-prem blueprints? Do we have to solve some similar issue there as well?

Acceptance Criteria:

• Have a discussion on the topic.
• If there is an agreement for a solution, do the following (or maybe a different solution if we agree on some):
  • Verify that it is possible to import a blueprint that would fill in the default subscription on import.
  • Verify that it is possible to import a blueprint that has unchecked subscription on import.

Related threads on Slack (September 4th messages)

• https://redhat-internal.slack.com/archives/C05LNKHBCDA/p1724661957329459
• https://redhat-internal.slack.com/archives/C05LNKHBCDA/p1725261499969139
•