We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When implementing replacement of secret vars in agent policies here, we left out a scenario when the variables can have array values.
See thread here for more info.
Expected fix: check if vars have array values, replace secrets in them.
To reproduce:
secret: true
- name: api_token type: text title: API Token multi: false required: true show_user: true description: The Alienvault OTX API token secret: true
request.transforms
streams: - id: httpjson-ti_otx.threat-a520c8d4-1c8e-48c6-8525-d046ab1b8bda data_stream: dataset: ti_otx.threat type: logs config_version: '2' interval: 5m request.method: GET request.tracer.filename: ../../logs/httpjson/http-request-trace-*.ndjson request.url: 'https://otx.alienvault.com/api/v1/indicators/export' request.timeout: 30s request.transforms: - set: target: header.Content-Type value: application/json - set: target: header.X-OTX-API-KEY value: '${SECRET_0}'
The text was updated successfully, but these errors were encountered:
Moving into current sprint as I think @michel-laterman has some time. Michel, would you please take a look at this?
Sorry, something went wrong.
michel-laterman
Successfully merging a pull request may close this issue.
When implementing replacement of secret vars in agent policies here, we left out a scenario when the variables can have array values.
See thread here for more info.
Expected fix: check if vars have array values, replace secrets in them.
To reproduce:
secret: true
to the manifest locally:request.transforms
should be replaced.The text was updated successfully, but these errors were encountered: