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
Add releases and flux runtime pages #1451
Conversation
@@ -119,7 +119,7 @@ service Apps { | |||
*/ | |||
rpc ListKustomizations(ListKustomizationsReq) returns (ListKustomizationsRes) { | |||
option (google.api.http) = { | |||
get : "/v1/namespace/{namespace}/app/{app_name}/kustomization" | |||
get : "/v1/kustomizations" |
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.
Nit: should this be plural? Usually the REST semantics are /v1/kustomization, I would expect a list. Then /v1/kustomization/:id, I would expect to get one.
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.
Sure, but not sure why we would try to min/max this as a REST API. I would hope someone would use the open API output to generate a client library in their language of choice.
We already gen the go
and ts
clients. I didn't have to change anything in my "user space" code to accommodate this change.
Good progress being made 👍 thanks Jordan Some comments:
Sources page
Flux Runtime page
|
Fixed
@joshri is working on that
Fixed
Follow up created: #1459
Fixed
Added, but we need to think about what this means for Helm/Bucket
Interval added
Fixed, but a
Added |
56aa620
to
6e2a446
Compare
d4e11c3
to
c3c8d36
Compare
c3c8d36
to
65799bf
Compare
Many thanks @jpellizzari
Both still have
Fair point, I wouldn't expect the flux controllers to though? Or am I missing something? |
|
||
list := &appsv1.DeploymentList{} | ||
|
||
if err := k8s.List(ctx, list, client.InNamespace(msg.Namespace)); 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.
I think we should avoid making assumptions about flux namespace (https://github.com/weaveworks/weave-gitops/pull/1451/files#diff-35acf2adc3a7b1021fb41d3473b47e030d3708ba2e8ff7a4b76c13ee80b4076cR42) and grab it by using something like: https://github.com/weaveworks/weave-gitops/blob/v2/pkg/kube/kubehttp.go#L496
I'm not sure we want to keep that interface but the actual method is useful.
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.
@luizbafilho Since we allow the client to specify the namespace
, can I fetch the correct namespace in a different call (in a future PR)?
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.
Yeah, it would be a good follow up issue
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.
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.
Front end looks stunning but I'll leave the approval to the back end experts
@sympatheticmoose are all sortable fields intended to have a sort arrow? Right now only the field that is actively being sorted has one
|
||
export default styled(KubeStatusIndicator).attrs({ | ||
className: KubeStatusIndicator.name, | ||
})``; |
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.
💕 ❤️ 💕
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.
@sympatheticmoose are all sortable fields intended to have a sort arrow? Right now only the field that is actively being sorted has one
I believe that is the design... @bia could you confirm? I am assuming the column header is clickable and thats what applies/flips the sort?
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.
Yes, in the current design only the field that is actively being sorted has an arrow (facing up or down based on sort direction). The other column headers that can sort the table should be clickable and the sort would be applied on click.
"type", | ||
"cluster", | ||
"status", | ||
"last synced at", |
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'm curious if my sort is handling "last synced at" correctly...
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.
Probs not; we will need to add the concept of data types.
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.
Adds the list pages according to the provided designs https://www.figma.com/file/IVHnM9iyeFWpd11evtY8ux/Weave-GitOps?node-id=5399%3A12874
Releases/Applications:
Sources Page:
Flux Runtime:
Note that this branch will not work for local development because of other broken things on
v2
. See this patch for more details: https://gist.github.com/jpellizzari/115de69875911c37cb6b0c0edc38e20c