design pattern for classes inside inventory

[Pranav Gupta]

Hi mentors and students,

In the task a single common.yml is mentioned inside classes folder.

So far I have clearly understood that targets link to the yml files inside classes folder which in turn contain parameters and subsequently link to the templated files which can be compiled to generate final configuration files. Now as seen in these examples  we usually break our project into multiple components (like scripts, docs, nginx(in our case)) etc and then a common.yml file can be used for configuration common to all components. So is it fine organizing in this way or we have to put all things under single common.yml ( as shown in task) and use it as the single target.

Thanks for helping out!

Pranav

[Pawel Sarbinowski]

Hi Pranav, 

The organisation mentioned in the task is mainly a guideline aimed to help students and isn't obligatory. 

You can structure the inventory however you want, as long as it compiles, and produces valid configs and run.sh is actually running.

Best,

Pawel

--
You received this message because you are subscribed to the Google Groups "kapitan-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kapitan-discu...@googlegroups.com.
To post to this group, send email to kapitan...@googlegroups.com.
Visit this group at https://groups.google.com/group/kapitan-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/kapitan-discuss/dafa9ef7-3362-42a9-b4bc-3d1ca1c93c7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Pawel Sarbinowski |

DevOps Engineer |

paw...@google.com

[Pranav Gupta]

Thanks