-
Notifications
You must be signed in to change notification settings - Fork 46
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
[#1693] Move defaults to airy yaml #1700
Conversation
return color.Colorize(color.Cyan, "#\t"+input) | ||
}) | ||
provider := providers.MustGet(providers.ProviderName(providerName), w) | ||
overrides := provider.GetOverrides() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of passing the overrides as --set
flags we merge them into the airy.yaml
first before using it as a values file in Helm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created a cluster and AWS and the annotation for the loadbalancer was not picked-up (classical loadbalancer was created).
} | ||
|
||
//go:embed src | ||
var templateDir embed.FS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Refactored the templating part of the workspace module into its own module
if err != nil { | ||
return err | ||
} | ||
if _, err := os.Stat(dstPath); err == nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a bug: The create
command was previously overwriting config that was already present.
@@ -6,6 +6,9 @@ go 1.16 | |||
// Automatically generated by running //tools/update-deps | |||
|
|||
require ( | |||
github.com/Masterminds/goutils v1.1.1 // indirect | |||
github.com/Masterminds/semver v1.5.0 // indirect | |||
github.com/Masterminds/sprig v2.22.0+incompatible // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the same templating library that helm uses
data: | ||
HOST: {{ .Values.global.host }} | ||
HOST: {{ .Values.global.kubernetes.host }} | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hoisted the security
configmap to the top level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the order in which we generate the airy.yaml
file should be:
- we grab the helm defaults
- we grab the overrides for a specific provider
- we provision
Airy core
in the Kubernetes cluster add grab the generated values (such ashost
) - we generate the
airy.yaml
file at the end
return color.Colorize(color.Cyan, "#\t"+input) | ||
}) | ||
provider := providers.MustGet(providers.ProviderName(providerName), w) | ||
overrides := provider.GetOverrides() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created a cluster and AWS and the annotation for the loadbalancer was not picked-up (classical loadbalancer was created).
In an offline conversation @ljupcovangelski and I decided that the best move forward would be to:
To improve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested and it works great 🎉
resolves #1693