Do you think this plus the relationship syntax (including the
many to many resulting from relationships between collections)
essentially cover the concerns, or are there more steps we should
be planning on taking?
its going to suck explaining to newbies but I think it does all it
needs.
What will suck to explain?
I want to make sure we ship with good docs for this, so having a
heads-up on what you think is confusing would help.
I need to work on some way to run test branches to really say or
sure but it seems ok
I'm leaning back toward restricting stages to only classes. I'm
concerned that the usability cost of the wild west there could be so
high that it will eliminate the benefits we're getting from it -
people will just consider them magical and dangerous, rather than
useful. What do you think?
Please consider restricting cross-stage relations instead. Either the
dependency goes along the stage-flow, then it is only necessary for
notification OR it goes against the flow, then it is illegal.
Execution-wise, stages would become self-contained compartments, which
should be easy to grasp conceptually. Having a simple way to get an
(ordered) list of stages and their resources, might help with
debugging/visualizing. Perhaps by extending the graph output and
accessing it in the dashboard?
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
