naml

What's Changed

• now using the new embed feature by @kris-nova in https://github.com/kris-nova/naml/pull/106
• Issue 105 by @kris-nova in https://github.com/kris-nova/naml/pull/107

Full Changelog: https://github.com/kris-nova/naml/compare/v1.0.2...v1.0.3

Looks like a lot of users are interested in the codify feature.

This is starting to get us closer to a somewhat decent autogen starting point. We still have a lot of reflection and importing to do, however this is getting stronger for most of the daily use cases.

What's Changed

• Issue 99 by @kris-nova in https://github.com/kris-nova/naml/pull/100
• Issue 101 by @kris-nova in https://github.com/kris-nova/naml/pull/102
• compile time poddisruptionbudget check by @kris-nova in https://github.com/kris-nova/naml/pull/103
• Unit tests (anchore, and contour) by @kris-nova in https://github.com/kris-nova/naml/pull/104

Full Changelog: https://github.com/kris-nova/naml/compare/v1.0.1...v1.0.2

Fixing a minor problem with NAML applications

They are now displaying their Version instead of the global NAML Version which is now hard coded as a default in the library.

The first major stable release

• Fixed dependency on temporary valast workaround
• Substantial YAML tests
• Deprecate RPC
• Flexible Deployable

This one should be here to stay for some time 🎉

Updating Version with AUR

Release Candidate for 1.0.0

• Still waiting on #30
• This breaks the Deployable interface
• This requires updates to vendoring go.mod projects
• Documentation
• Adding YAML unit tests
• Library feature
• Remove RPC
• Alias unit tests
• List improvements
• Output checks

Adding support for 2 new kubernetes object types

• IngressClass
• ValidatingWebhookConfiguration

Note: This requires a "Go" binary on the host system.

naml build main.go
naml build app.go
naml build main.go -o app.naml

Adding some YAML tests and working -o yaml tested with the Kube dashboard

Bumping a release with the work around for int32 and in64 pointers in naml codify.

Cutting from head for vendoring a new repo

Naml now supports -o yaml

naml -o yaml
naml output AppName -o json
naml output
naml output AppName -o yaml

Other features

• Integration test for yaml -> go -> compile -> run
• Improvements to generating packages
• Improvements to CLI langauge

Adding new features with codify

• Output
• Better debug
• GoName

Go modules make me cry - like in the sad way. They really hurt me.

Anyway this release exists just to prevent the HTTP 410 error whilst trying to vendor 0.2.4

Closing #45
Embedding improvements
Updating go mod release tag

This addresses the

../go/pkg/mod/github.com/kris-nova/[email protected]/codify.go:104:23: undefined: FormatMainGo

error with 0.2.1 and 0.2.2

This also now adds logging to stderr for the naml codify command (if something goes wrong)

Updating the naml codify feature.

Now working with the following Kubernetes objects in the codify package. I was able to generate working go code from entire namespaces.

• corev1.Pod
• appsv1.Deployment
• appsv1.StatefulSet
• appsv1.DaemonSet
• corev1.ConfigMap
• corev1.Service
• corev1.PersistentVolume
• corev1.PersistentVolumeClaim
• batchv1.Job
• batchv1.CronJob
• rbacv1.Role
• rbacv1.ClusterRole
• rbacv1.RoleBinding
• rbacv1.ClusterRoleBinding
• networkingv1.Ingress
• appsv1.ReplicaSet
• corev1.Endpoints

Releasing the new codify feature. This feature is still in alpha. Use responsibly.

There is a new (alpha) feature codify that will attempt to generate as much go code as possible for existing Kubernetes YAML.

You can pipe valid Kubernetes .yaml to naml codify and it will do it's best to generate as much code as possible for you. This will work best if you know what you are doing and just want a place to get started coding.

Currently the following types are supported. If there is a type that you are looking for that isn't here feel free to open a pull request or submit an issue and I will add it as soon as I can.

• Service
• ConfigMap
• Deployment
• StatefulSet
• DaemonSet
• Deployment
• Pod
• List

You can use the codify feature like this:

kubectl get deploy -oyaml | naml codify > main.go
cat configmap.yaml | naml codify > main.go
helm template chart | naml codify > main.go

Adding .Description() string to the Deployable interface.

After some thought I do believe that the interface is a viable starting point.

I have decided NOT to add the following for this initial release

• Reconcile()
• List()
• Get()
• IsInstalled()

I believe these are out of scope, and in theory should be handled by another system (such as a controller or operator).

Determining if an application needs to be installed or uninstalled is out of scope.

We just are here for a user to call .Install() or .Uninstall() when they deem necessary.

Minor doc tweaks and updating client.go and registry.go

This should vendor reasonable well by now