Skip to tutorial content
Rate module Not yet rated

Packaging and Promoting the Pattern Safely

4 min read
On this page

In this lesson, you will learn:

  • What must move together
  • How to package it
  • How to test before production

🔁 Quick look back: Last time: Debugging and Validating the Pattern. You learned how the archiver pattern was tested and linked to nightly scans.

1 The Problem: A Pattern Without Its Class Fails in Production

The archiver needs several pieces: a class, fields, an identification rule, a pattern, an IP service and a classifier. If one is left behind:

  • The pattern fails in production.
  • Or it creates CIs in the wrong class.

🎯 The problem: A pattern moved without its other pieces fails.

👉 The fix: Package every piece together and test the move on snwrstage.

Table of pieces to move.
Figure 1. Everything that moves with the archiver pattern.

2 Packaging

  • Capture every piece in one update set.
  • List the pieces in the migration matrix.
  • Keep the pattern in its own set if you’ll update it often.

💡 Good to know: Need a refresher? See Fundamentals › Update Sets for update set basics.

3 Testing the move

  1. Move to snwrstage first.
  2. Check every piece arrived.
  3. Run Quick Discovery against a test target.
  4. Then promote to snwr through change.

4 Project Clear View: How We Implemented It

📍 Situation: The archiver was ready on snwrdev.

🧭 Decision: Package all pieces and rehearse on snwrstage.

🛠️ Steps we took:

  1. Captured the five pieces in one update set.
  2. Listed them in the migration matrix.
  3. Moved to snwrstage with Riya and checked each piece.
  4. Scheduled the snwr move with the production rollout.

✅ What we verified:

  • All pieces arrived on snwrstage.
  • The rehearsal found nothing missing.

📁 Evidence: The archiver update set, in the migration matrix (see Production Rollout › Building the Production Migration Matrix).

5 Quick recap

  • A custom pattern has many pieces.
  • Package them together.
  • Rehearse the move on staging.
  • Promote to production through change.

6 Check yourself

Think of your answer first. Then tap to check.

1 Name three pieces that move with the archiver pattern. Show answer

Any three of: class and fields, identification rule, pattern, IP service, process classifier.

2 Where did SNWR rehearse the move? Show answer

snwrstage.

3 What happens if the class is left behind? Show answer

The pattern fails, or CIs land in the wrong class.

Nice work! The archiver is ready for production. 🎉
Next up: How Cloud Discovery Works: API vs IP

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.