Skip to content
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

feat: add basic support for helm charts #118

Merged
merged 6 commits into from
Jun 14, 2018
Merged

feat: add basic support for helm charts #118

merged 6 commits into from
Jun 14, 2018

Conversation

edvald
Copy link
Collaborator

@edvald edvald commented May 25, 2018

Implementation note: We're not actually using helm to perform the
install, since it proved unreliable and opaque. We instead use helm
to render the templates and provide an array of specs that we feed
to kubectl apply. This also avoids the need for installing tiller,
which will be removed in Helm 3 either way. We may reconsider this
approach when Helm 3 is out and stable.

@edvald edvald requested a review from eysi09 June 5, 2018 13:08
@edvald
Copy link
Collaborator Author

edvald commented Jun 5, 2018

Found a bug after rebase-ing, looking into it

@edvald edvald changed the title feat: add basic support for helm charts [WIP] feat: add basic support for helm charts Jun 5, 2018
@edvald edvald changed the title [WIP] feat: add basic support for helm charts feat: add basic support for helm charts Jun 13, 2018
@edvald
Copy link
Collaborator Author

edvald commented Jun 13, 2018

This npm package-lock issue will be the end of me

@thsig thsig self-assigned this Jun 14, 2018
}

await apiPostOrPut(coreApi(context).namespaces(ns).configmaps, resultKey, body)
try {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would be cleaner to abstract this repeated try/catch pattern around the coreApi calls with something similar to the old apiPostOrPut function that was removed in this commit?

8ccd9a1#diff-1300351cb8f4f405710841426a313b36L37

Maybe something like await coreApiRequest(tryFn, catchFn, statusCode)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants