ship

ship copied to clipboard

### Expected behavior - go to `/kustomize` step - Edit patch for a resource - save and continue - click back to kustomize step (or browser back button) - click...

dexhorthy

Ship.yaml should not always create an installer directory

1

### Expected behavior When installing an app from a ship.yaml, the output should only create directories and files that were specified in the ship.yaml. ### Actual behavior An empty "./installer"...

marccampbell

ship init: bufio.Scanner: token too long

2

When running ship init on a chart with a very large secret (approx a 122KB secret), ship init errors out with: `execute render step: execute plan: execute templating: unable to...

wstrange

We currently refer to the Replicated documentation for the config yaml options, but there are a lot of subtle differences. (removal of legacy `when` behavior, etc)

laverya

We currently refer to the Replicated documentation for template functions, but there are a lot of template functions in Ship that aren't in Replicated and vice-versa.

laverya

### Expected behavior When adding markdown (or html) to a help_text item, the renderer should render it properly, using template functions and turn it into html for display. ### Actual...

marccampbell

### Expected behavior The config section of a `ship.yaml` should support a label type to be consistent with the documentation. ### Actual behavior Label type is ignored and not rendered...

marccampbell

### Expected behavior `ship init` runs properly with all kubernetes upstreams. ### Actual behavior When running with certain kubernetes yaml upstreams such as `https://cloud.weave.works/k8s/net?k8s-version=1.11.5&omit-support-info=true`, `ship init` will error when reaching...

laverya

`ship update` should work after `ship init` even if no lifecycle was provided

2

### Expected behavior `ship update` should work after `ship init` even if no lifecycle was provided ### Actual behavior If no lifecycle was provided (leading to the default k8s lifecycle...

laverya

We should add a base image that we can use in CircleCI for integration so we don't have to download dependencies on every run. The image in `integration/Dockerfile` could be...

ebramanti