Skip to content

add password_file when converting to Prometheus basic_auth#82

Closed
rfratto wants to merge 1 commit into
grafana:masterfrom
rfratto:add_password_file
Closed

add password_file when converting to Prometheus basic_auth#82
rfratto wants to merge 1 commit into
grafana:masterfrom
rfratto:add_password_file

Conversation

@rfratto

@rfratto rfratto commented May 20, 2020

Copy link
Copy Markdown
Member

Fixes #81

@rfratto

rfratto commented May 21, 2020

Copy link
Copy Markdown
Member Author

This fix isn't sufficient enough to fix all the problems v0.3.0 introduced; see #86. I'm going to close this in favor of a better solution that I'll publish later today.

@rfratto rfratto closed this May 21, 2020
@rfratto rfratto deleted the add_password_file branch May 21, 2020 12:27
rfratto referenced this pull request in rfratto/agent May 21, 2020
Fixes #86
Fixes #81 (because it removes the broken)
Supplants #82
rfratto added a commit that referenced this pull request May 21, 2020
* add yaml hook to not marshal secrets as "<secret>"

Fixes #86
Fixes #81 (because it removes the broken)
Supplants #82

* replace other uses of yaml marshaling a config with the package methods

* add in protection that prevents instance configs from being marshaled directly

instance.Configs should always be marshaled to YAML through the marshal
functions within the instance package, never using the YAML package
directly.

* allow "normal" marshaling of instance.Config to keep secrets intact

Marshaling without the custom methods will now be slower but will at
least work and not unexpectedly remove secrets. Calling the custom
methods is still required for scrubbing secrets.

* add test to validate instance config marshaling
mattdurham pushed a commit that referenced this pull request Nov 11, 2021
* add yaml hook to not marshal secrets as "<secret>"

Fixes #86
Fixes #81 (because it removes the broken)
Supplants #82

* replace other uses of yaml marshaling a config with the package methods

* add in protection that prevents instance configs from being marshaled directly

instance.Configs should always be marshaled to YAML through the marshal
functions within the instance package, never using the YAML package
directly.

* allow "normal" marshaling of instance.Config to keep secrets intact

Marshaling without the custom methods will now be slower but will at
least work and not unexpectedly remove secrets. Calling the custom
methods is still required for scrubbing secrets.

* add test to validate instance config marshaling
wildum pushed a commit that referenced this pull request Apr 9, 2024
There is only one release asset, so we don't need nested folders in
packaging/.
@github-actions github-actions Bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label May 4, 2024
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators May 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

remote_write config stanzas ignore password_file

1 participant