Horizontal Patterns of type "2 - Shared Library" / Kubernetes Horizontal Patterns

[Todd_Goodhew]

For Horizontal Patterns of type "2 - Shared Library", does anyone have experience with either editing an existing horizontal pattern or creating a new pattern?  If so, what's the secret?

I have a need to update a couple of the existing patterns related to Kubernetes to pull back some more attributes.  I'm struggling on where to start.  The are all of type "2 - Shared Library" and don't open the Pattern Editor like infrastructure or application patterns.

I also need to create a new pattern to get other objects out of Kubernetes.  How do I create a new pattern when "Shared Library" is not a listed pattern type?

[sethivarun]

as per best practices you shouldn't modify the shared patterns. If you have to use them you can add steps in extension section or in the pattern itself that uses a shared pattern

[Todd_Goodhew]

I just figured out that "2 - Shared Library" is a shared pattern.  Didn't know the before hand.

Also, now understand how to see them in the editor.  Needed to locate the pattern that calls the shared patterns.  In the case of Kubernetes, I needed to open the pattern named "Kubernetes" of the type "3 - Infrastructure".   

Looks like I have some more learning to do in order to follow the best practice as noted above by sethivarun.

[robertgeen]

Todd,

Honestly the best practice gets a little tricky when you talk about shared patterns as it's very difficult to clone them or to "extend" them like they want. Also due to the fact that they may get called in the middle of a identification or connection section it's really difficult to follow the whole used an extension section.

I've never done it before if there is something you can't do easily in an extension and you need to customize the core shared library you may be able to insert/stay on the record for the shared library and then call it in a pattern and modify the new one from there. Either way it is definitely a bit tricky and depending on what you need to do there are a few options. If you just want to add additional attributes to a CI or something then i would recommend the extension section however if it's a fundamental step in the shared library then you may have to go down the other path I was talking about. Hope this helps.

[Todd_Goodhew]

Thanks for the info.

I think I figured out my way forward on this.

I'm going to edit the shared libraries via a parent pattern.  When I save, I get an option to save the shared libraries which I'll do.  The doco says these all get versioned and any upgrade will only update the original base pattern and not touch my versions.  I can revert versions at any time if I need to get back to OOTB.

I also realized I don't need to create a new pattern.  Instead I need to add some steps and convert them to a shared library, then make sure that shared library is called by the other pattern.  There are 2 infrastructure Kubernetes patterns that call all the shared libraries.  I understand why there are 2 and how they work together.