Document the intended design and data model #47
Conversation
| The various versions of an application are stored as bindles. A bindle associated with | ||
| an application is called a _revision_. Revisions don't do anything in themselves - | ||
| they just record that Hippo knows about the bindle and which application is belongs to. | ||
| **NOTE: We're not sure if this is what revisions model in the existing code - may need |
There was a problem hiding this comment.
This checks out:
https://github.com/deislabs/hippo/blob/main/Hippo/Models/Application.cs#L26
https://github.com/deislabs/hippo/blob/main/Hippo/Models/Release.cs
Right now we call it a "Release" rather than a "Revision", but I think "Revision" better suits the model we're going after. So perhaps we should change the class name to match. Because it's not actually "released" until a channel selects it.
As we discussed earlier, the Revision field in the Release object is just duplicated data that we can probably infer from the bindle reference URL.
docs/community/design-model.md
Outdated
| of an application, but you can use them for any situation where you want to have | ||
| different versions or different configurations. | ||
|
|
||
| > The weather application might have channel's named `development` (for work in progress), |
There was a problem hiding this comment.
omg no curls up into a ball of failure and refuses to come out until summer
docs/community/design-model.md
Outdated
| different versions or different configurations. | ||
|
|
||
| > The weather application might have channel's named `development` (for work in progress), | ||
| > `staging` (for pre-production testing) and `production` (for the live site). |
There was a problem hiding this comment.
needs a comma after "testing)" to note that "production" is a separate line item.
Per discussion with @bacongobbler on the channel model.