-
Notifications
You must be signed in to change notification settings - Fork 32
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
POL-1378 Linting Updates: Operational Policies #2732
Conversation
Generated by 🚫 Danger |
@@ -226,11 +226,11 @@ end | |||
datasource "ds_current_products_oldconnection" do | |||
iterate $ds_bill_connections_old | |||
request do | |||
run_script $js_get_products_oldconnection, val(iter_item, 'id'), $ds_top_level_bcs, rs_org_id, rs_optima_host, 3 | |||
run_script $js_get_products_oldconnection, val(iter_item, 'id'), $ds_top_level_bcs, 3, rs_org_id, rs_optima_host |
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 think this was fine before
run_script statements found whose parameters are not in the correct order. run_script parameters should be in the following order: script, val(iter_item, string), datasources, parameters, variables, raw values:Line 229: ds_current_products_oldconnection / run_script $js_get_products_oldconnection
Line 325: ds_current_products_newconnection / run_script $js_get_products_newconnection --
run_script $js_get_products_oldconnection, val(iter_item, 'id'), $ds_top_level_bcs, 3, rs_org_id, rs_optima_host | |
run_script $js_get_products_oldconnection, val(iter_item, 'id'), $ds_top_level_bcs, rs_org_id, rs_optima_host, 3 |
(Would obviously mean lines 243, 255, 325, 339 and 351 would need to be reverted)
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.
Nvm, I see why you did this
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.
LGTM
Description
Various small changes to Security policies to bring them up to current linting standards. Also removes known bad coding patterns to avoid their reuse.
Dangerfile error is a false positive and can be ignored. The coding pattern causing it is sufficiently niche to not be worth the effort of coding the Dangerfile test around it.