Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

Missing keys in file reference? (replicas and labels) #104

Closed
cdrage opened this issue Jun 29, 2017 · 15 comments
Closed

Missing keys in file reference? (replicas and labels) #104

cdrage opened this issue Jun 29, 2017 · 15 comments

Comments

@cdrage
Copy link
Collaborator

cdrage commented Jun 29, 2017

Bit confused by the file reference here:
https://github.com/kedgeproject/kedge/blob/master/docs/file-reference.md

I see that we have "replicas" and "labels" but it does not indicate it's not yet implement nor it's in the example.

@cdrage cdrage changed the title Missing keys in file reference? Missing keys in file reference? (replicas and labels) Jun 29, 2017
@cdrage
Copy link
Collaborator Author

cdrage commented Jun 29, 2017

Another thing to note is "ingresses" is in the full example at the bottom, but not in the reference example at the top.

@kadel
Copy link
Member

kadel commented Jun 30, 2017

I see that we have "replicas" and "labels" but it does not indicate it's not yet implement nor it's in the example.

not yet implemented? both 'replicas' and 'labels ' are implemented

@surajssd
Copy link
Member

Another thing to note is "ingresses" is in the full example at the bottom, but not in the reference example at the top.

To keep example shorter we only added the key endpoint which also generates the default ingress, so it is not shown there.

ingresses root level field is for people who wanna specify ingress by themselves.

@cdrage
Copy link
Collaborator Author

cdrage commented Jun 30, 2017

@kadel Ah okay, it's a docs issue then. There's no example on either the bottom or the top that shows how it's implemented in a full file.

@cdrage
Copy link
Collaborator Author

cdrage commented Jun 30, 2017

@surajssd Okay, we should show how we use it then in an example.

@kadel
Copy link
Member

kadel commented Jun 30, 2017

I'm not a big fan of showing everything in one file, to be honest, it looks scary, it's hard to read, and I doubt that any application will ever use every feature there is.

@pradeepto
Copy link
Member

I'm not a big fan of showing everything in one file, to be honest, it looks scary, it's hard to read, and I doubt that any application will ever use every feature there is.

I am confused about this because this is supposed to be a file reference. Should the example not have every feature? Maybe we need a middle path.

Ok, how about having smaller examples at "key" level? Not necessarily for all keys but some keys that we think are important. Often you see such examples in API docs where small focused snippet (partial code) are provided for certain methods showcasing usage of that method.

@kadel
Copy link
Member

kadel commented Jun 30, 2017

👍 for multiple small examples highlighting features that are documented in given section

@surajssd
Copy link
Member

@cdrage
Copy link
Collaborator Author

cdrage commented Jun 30, 2017

@kadel @surajssd Okay. Smaller examples 👍 but let's get some examples into the file reference doc, not putting docs in the examples folder.

@pradeepto
Copy link
Member

File reference should have snippets only and not whole examples or it becomes just a long file that people will get lost in. Of course, in a certain case where it is important to show the whole example, we do that. Use your best judgement.

@pradeepto
Copy link
Member

And we should definitely have the examples folder, it is a great learning resource.

@pradeepto
Copy link
Member

@cdrage @kadel @surajssd @containscafeine What is the resolution here? And what would be the action items?

@cdrage
Copy link
Collaborator Author

cdrage commented Jul 11, 2017

@pradeepto I believe we can resolve this in #136 as well as doing minor updates to the file reference doc to avoid any confusion in regards to missing keys.

@cdrage
Copy link
Collaborator Author

cdrage commented Nov 8, 2017

Now that http://kedgeproject.org/file-reference/ has been created, it's quite clear that you are able to "extend" the Kedge file with Pod concepts, and thus, replicas is clearly documented. Closing this issue.

@cdrage cdrage closed this as completed Nov 8, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants