-
Notifications
You must be signed in to change notification settings - Fork 4
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
Singular ClamAV instance #2660
Singular ClamAV instance #2660
Conversation
…CAN enpoint to tanf-prod clam av scanner only
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2660 +/- ##
===========================================
- Coverage 92.99% 92.75% -0.25%
===========================================
Files 219 235 +16
Lines 4482 5201 +719
Branches 385 452 +67
===========================================
+ Hits 4168 4824 +656
- Misses 242 290 +48
- Partials 72 87 +15
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
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 believe we need to ensure network-policy are added that enables non-prod instances to talk to the prod clamav. Should only be a couple lines in deploy-backend.sh.
@andrew-jameson |
Question: does this require us to share prod space keys with dev? @George-Hudson |
@ADPennington @andrew-jameson that is unclear. The documentation does not mention it and it doesn't make sense to me to do it this way. I would think it's more of a dns routing issue and less of an internal networking issue. We currently don't establish a network policy in order to connect to in-space clamAV servers, so I am not sure if we need it to reach a different-cf-space clamAV server. |
tdrs-backend/clamav-router/README.md
Outdated
@@ -0,0 +1,49 @@ | |||
# CLAMAV |
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.
Need to consolidate this with the README file in /Technical-Documentation
@@ -107,6 +106,17 @@ update_backend() | |||
# Add network policy to allow frontend to access backend | |||
cf add-network-policy "$CGAPPNAME_FRONTEND" "$CGAPPNAME_BACKEND" --protocol tcp --port 8080 | |||
|
|||
if ["$CF_SPACE" = "tanf-prod" ]; then | |||
# Add network policy to allow backend to access tanf-prod services | |||
cf add-network-policy "$CGAPPNAME_BACKEND" clamav-rest --protocol tcp --port 9000 |
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.
Question: Do we need to set the AV_SCAN_URL in prod?
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.
we definitely need the env var in prod
scripts/deploy-backend.sh
Outdated
@@ -40,7 +40,6 @@ set_cf_envs() | |||
"AMS_CLIENT_ID" | |||
"AMS_CLIENT_SECRET" | |||
"AMS_CONFIGURATION_ENDPOINT" | |||
"AV_SCAN_URL" |
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.
The env var cannot come from outside envs since it is dynamic
} | ||
server { | ||
listen 9000; | ||
location /scan { |
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.
This opens a route to clamav prod, we might want to add a note somewhere for revising this later on. Although all traffic is from cloud.gov space, but they are from a space out of prod
Testing this on cloud.gov, it looks like cloud.gov doesn't allow opening any port in NGINX other than default 8080. Still investigating to see if there is any other way to do this |
…cies in the deploy-backend.sh script
GitHub isn't showing the changes to scripts/deploy-backend.sh for this PR going to close this and remake |
…CAN enpoint to tanf-prod clam av scanner only
Summary of Changes
Provide a brief summary of changes
Pull request closes #2429 _
How to Test
Deploy the branch to one of the dev/staging instances and then follow the steps below:
Deliverables
More details on how deliverables herein are assessed included here.
Deliverable 1: Accepted Features
Checklist of ACs:
lfrohlich
and/oradpennington
confirmed that ACs are met.Deliverable 2: Tested Code
CodeCov Report
comment in PR)CodeCov Report
comment in PR)Deliverable 3: Properly Styled Code
Deliverable 4: Accessible
iamjolly
andttran-hub
using Accessibility Insights reveal any errors introduced in this PR?Deliverable 5: Deployed
Deliverable 6: Documented
Deliverable 7: Secure
Deliverable 8: User Research
Research product(s) clearly articulate(s):