-
Notifications
You must be signed in to change notification settings - Fork 0
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
Clean up code #98
Clean up code #98
Conversation
# add route for auth proxy job | ||
- type: replace | ||
path: /instance_groups/name=opensearch_dashboards/jobs/name=route_registrar? | ||
value: | ||
consumes: | ||
nats-tls: | ||
deployment: cf-development | ||
from: nats-tls | ||
name: route_registrar | ||
properties: | ||
route_registrar: | ||
routes: | ||
- name: opensearch-auth-proxy | ||
registration_interval: 2s | ||
server_cert_domain_san: auth-proxy.opensearch.internal | ||
timeout: 1s | ||
tls_port: 8000 | ||
release: routing | ||
|
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 is handled below by lines 115-131
deploy-logs-opensearch/opsfiles/enable-proxy-auth.yml
Lines 115 to 131 in a136d40
- type: replace | |
path: /instance_groups/name=opensearch_dashboards/jobs/name=route_registrar? | |
value: | |
consumes: | |
nats-tls: | |
deployment: ((cf-deployment)) | |
from: nats-tls | |
name: route_registrar | |
properties: | |
route_registrar: | |
routes: | |
- name: opensearch-auth-proxy | |
registration_interval: 2s | |
server_cert_domain_san: auth-proxy.opensearch.internal | |
timeout: 1s | |
tls_port: 8000 | |
release: routing |
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.
looks good- good cleanup
Changes proposed in this pull request:
Things to check
INFO
and debugging statements are written withlog.debug
or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.Security considerations
None, just cleaning up code