This message was deleted.
# neuvector-securitya
adamant-kite-43734
08/15/2024, 3:13 PMThis message was deleted.
i
important-activity-72202
08/15/2024, 3:39 PMI tried placing a policy file in the repository, but neuvector never seems to fetch the configuration. I also tried to upload a policy file directly from neuvector, and it fails with 'Error happens when exporting group configuration file!'.
important-activity-72202
08/15/2024, 3:44 PMThe controller log says: "2024-08-15T153904.775|ERRO|CTL|rest.doExport: could not do remote export - error=could not do github export: non-OK status response: &{404 Not Found 404 HTTP/2.0"
I guess I need to check the personal access token again. It might be expired
important-activity-72202
08/15/2024, 4:22 PMToken was not expired, I tried to create new tokens (classic and the new kind), and now I can upload a policy from neuvector to github, but then it just stays there. Neuvector does not apply the rule. Maybe it only works with classic tokens.
q
quaint-candle-18606
08/16/2024, 3:18 PMI was going to say that it is poorly documented, but like you see, it’s not documented at all. 😐 (I’ve raised this issue with the docs team)
quaint-candle-18606
08/16/2024, 3:21 PMThis is an early release of a feature that I think should be tagged as `public beta`; just my opinion. It’s a great step in the right direction, but in its current form, it essentially sends the CRD file to github
i
important-activity-72202
08/23/2024, 7:47 AMThanks, perhaps I expected to much from this "feature". I am very familiar with git and could also build some auto-deployment with argocd or similar. I was thinking this github feature is supposed to facilitate a git ops style management of neuvector. I am not so happy with the 'github' only configuration. Instead, I want to use my own gitlab instance. Perhaps this will be possible when the
public betaq
quaint-candle-18606
08/23/2024, 1:37 PMYeah, this feature will grow and improve, for sure. 🙂
3 Views