-
-
Notifications
You must be signed in to change notification settings - Fork 231
Use Sensitive for Secrets #973
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
base: master
Are you sure you want to change the base?
Conversation
I am mistaken or the |
8ea844a
to
fcf3799
Compare
Can you remove the non related edit from the commit? |
The rendered ERB-Template is wrapped, if the Password initially was given as content => if $database_password =~ Sensitive {
Sensitive(template('zabbix/web/zabbix.conf.php.erb'))
} else {
template('zabbix/web/zabbix.conf.php.erb')
}, |
The Github-Pipeline gave me Warnings about Indentation. So I corrected the Indentation, because I added Datatypes, which shifted the
I will not implement new Templates. I am only here to educate this Module using |
ok, I've misunderstud the TODO comment I'm checking the CI to fix the failure, next try to fix indentation |
Oh, I see. Maybe make sure it is the same in |
You are right. adapted the other sensitive rendered Templates also. Thanks. |
To not reveal Secrets, accept Datatype Sensitive. Render Templates as sensitive Content, if Secrets were given as Sensitive.
2f5fa95
to
1cbc5c9
Compare
I rebased against |
Can you try to check why it fails? |
Any chance this get merged before release 11?
Are this kind of timeout error simply solved by running the test again? |
Pull Request (PR) description
To not reveal Secrets, accept Datatype
Sensitive
. Render Templates as sensitive Content, if Secrets were given asSensitive
.This Pull Request (PR) fixes the following issues
Fixes #950
Addendum
@teluq-pbrideau 2022-12 also made a PR #857, which has not been merged yet.