Skip to content

feat: Add gitops environments resource#170

Closed
ilia-medvedev wants to merge 3 commits intomasterfrom
feat/add-gitops-environments
Closed

feat: Add gitops environments resource#170
ilia-medvedev wants to merge 3 commits intomasterfrom
feat/add-gitops-environments

Conversation

@ilia-medvedev
Copy link
Copy Markdown

What

Why

Notes

Checklist

@ilia-medvedev
Copy link
Copy Markdown
Author

/test

@ilia-medvedev
Copy link
Copy Markdown
Author

/test

@eti-codefresh
Copy link
Copy Markdown

i reviewed the platform side looks good to me

Copy link
Copy Markdown

@scme0 scme0 left a comment

Choose a reason for hiding this comment

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

lgtm

Comment on lines +48 to +53
"server": {
Type: schema.TypeString,
Optional: true,
Description: "Target cluster server url. Defaults to `https://kubernetes.default.svc` which is the default in-cluster url",
Default: "https://kubernetes.default.svc",
},
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

server should always correspond to the server of ArgoCD cluster we put in name and we don't have any validation for it on the backend. Putting random address in server can result in weird bug when in our UI we see that environment configured with cluster X, but inside it has apps from cluster Y.

What I think we should do is to remove "server" from graphql mutation input and derive it from the DB according to the provided cluster name. It should be easy change on backend side.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@denis-codefresh I agree. I did the implementation according to the current schema and it's a mandatory field

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants