vscode-gitops-tools
vscode-gitops-tools copied to clipboard
weaveworks
GitOps Visual Studio Code Extension
### Expected behaviour I deployed sealed secrets in my cluster according to the Flux documentation. I see the deployment in the extension. When I right-click on the deployment and select...
### Expected behaviour I right-click on a HelmRelease under Workloads in the extension. I expect the selected HelmRelease to be deleted from my Kubernetes cluster. ### Actual behaviour Instead, I...
Edit: Includes #270 (published as 0.20.0-alpha.2) I'd still like to omit the ManagedFields from the describe output, maybe this can be refactored to present as an option in the API...
### Expected behaviour When the `Disable GitOps` command is invoked, the generic Flux provider basically just invokes `flux uninstall` This is a very safe way to disable GitOps as it...
In the workflow for onboarding new Azure users, the customers get to choose between Azure Arc, or AKS. They don't really create the cluster in the VScode editor with the...
User feedback > it would be nice to have an amber state for things that are mid-reconcile and reserve red for when things have actually failed
Controlled Logs visual formatting should be improved, and should run and scroll to bottom initially
### Expected behaviour Expected GitOps to be enabled in the cluster. Expected workflow similar to the one presented in Simplify GitOps with Flux and Visual Studio Code (https://www.youtube.com/watch?v=-07emkW8eiM) by Geert...
[https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token) CI releases are blocked if this token expires, until it is replaced (the replacement token is created here): [https://dev.azure.com/weaveworks/_usersSettings/tokens](https://dev.azure.com/weaveworks/_usersSettings/tokens) I have got this on my personal calendar as a...
We have this landing page: https://marketplace.visualstudio.com/items?itemName=Weaveworks.vscode-gitops-tools But we should have a different page that we can use for hosting docs. Put them on a GitHub Pages site where we can...