allow abra to disable lint checks for service apps like backupbot #319
Closed
opened 2022-05-09 11:47:07 +00:00 by yksflip
·
5 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#319
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
there might be apps like backupbot that don't need traefik ingress routing, still abra checks them for traefik labels. I think it would be useful to disable the lint checks or some other way to deploy apps that violate the default linting...
@yksflip oh i see, do you have a proposal for the command line interface for this?
I was also thinking, maybe, since we tend to use the
proxynetwork as a naming convention for service which should have public internet access, we could just skip any service that doesn't have this network attached?Or potentially, only scan the
appservice & turn this error into a warning. Which would just mean you see a warning & can continue to run stuff.Maybe like this?
Scanning for the
proxynetwork is also a great idea!I think as long as it's possible to override checks manually I like them to fail. I tend to ignore warnings :D
Hey, newbie here. I'm currently adding the flag as an option. I am assuming you only want to pass this flag when you're deploying new apps, or is there another situation(s) where you would like the linter to be disabled? (UPDATE: I'm realizing the linter logic is scoped more accurately to recipes. I'll hold off from asking more questions until I've made it through this part of the codebase.)
Following chat in #354, seems like "no DOMAIN" could also be a decent heuristic for disabling this check.
Any preferences between that, and checking for
proxynetwork?#354 also revealed this is affecting
swarm-cronjob, so some kinda fix could be handy 🤔@3wordchant I think the domain check is best as there are often times when you route with the proxy network but you don't have a domain attached ("headless traefik" installs)?
Adding a check in the
LintFunctionmight be simplest. Idk if it will complicate the code much. Alternatively, we could add aConditionto14187449a5/pkg/lint/recipe.go (L22-L28)which checks for some stuff and then does or does not run the linting rule?