-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could do with some examples #2
Comments
Hi! The primary reason I made this library was for working with docker/kubernetes deployment configuration in albatross. The main use case there is for having separate templates which share a common weaver config in order to keep shared data in sync (e.g. referencing a stateful set's name from a service, using a generated docker image tag from a kubernetes stateful set, sharing as much config as possible between dev and prod deployments...). I use these libraries for primarily closed-source work at my full-time job, but I can pull some stuff in and remove any sensitive data. (I'm busy today, but I'll put something up this week.) I also think that the pattern of templating data could be useful in many other contexts as well, so I'll include some examples for custom tags as well. I haven't done much work to make this library accessible, but I'm happy to step it up a bit if people like you find it useful or interesting. Are there any specific features that you're looking for information on, or any specific things you're trying to accomplish with weaver? |
I watched your talk about scripting Kubernetes and thought this would be a
far better way to create k8s objects than Helm or something else that tries
to template YAML. So I think we're on the same page :)
…On Sun, 21 Jul 2019, 20:09 Scot Brown, ***@***.***> wrote:
Hi!
Yeah, that'd be good. Thanks!
The primary reason I made this library was for working with
docker/kubernetes deployment configuration in albatross
<https://github.com/SVMBrown/albatross>. The main use case there is for
having separate templates which share a common weaver config in order to
keep shared data in sync (e.g. referencing a stateful set's name from a
service, using a generated docker image tag from a kubernetes stateful set,
sharing as much config as possible between dev and prod deployments...).
I use these libraries for primarily closed-source work at my full-time
job, but I can pull some stuff in and remove any sensitive data.
I also think that the pattern of templating data could be useful in many
other contexts as well, so I'll include some examples for custom tags as
well.
I haven't done much work to make this library accessible, but I'm happy to
step it up a bit if people like you find it useful or interesting.
Are there any specific features that you're looking for information on, or
any specific things you're trying to accomplish with weaver?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=ABXBZYHKX7IBKJ3N3PKBRKTQASQ43A5CNFSM4IFSZ5Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OIUXQ#issuecomment-513575518>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABXBZYEL3Y3ZFPEXL6CC4RDQASQ43ANCNFSM4IFSZ5QQ>
.
|
Hey there!
Short of your tests, I'm kinda in the dark about how you use this code.
I'd happily work with you to come up with some examples - perhaps you could share a couple of really simple ones and we can work together to illuminate the features of Weaver from there?
The text was updated successfully, but these errors were encountered: