Skip to content
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

cannot enable WebService::Client logging in backends #14

Open
XSven opened this issue Nov 29, 2022 · 1 comment
Open

cannot enable WebService::Client logging in backends #14

XSven opened this issue Nov 29, 2022 · 1 comment

Comments

@XSven
Copy link

XSven commented Nov 29, 2022

WebService::HashiCorp::Vault extends WebService::HashiCorp::Vault::Base. WebService::HashiCorp::Vault::Base consumes the role WebService::Client. WebService::Client offers the attributes logger and log_method to enable logging. WebService::HashiCorp::Vault seems to be a kind of factory class for backend objects. I have now created an object of the WebService::HashiCorp::Vault class. I have passed values for the logger and the log_method attributes to the constructor. My expectation was that these attributes are passed to the corresponding backend object too, if I call the secret() object factory method.

Seemingly only some attributes

$args{approle}  = $self->approle();
$args{token}    = $self->token();
$args{version}  = $self->version();
$args{base_url} = $self->base_url();
$args{ua}       = $self->ua();

are passed from $self (refers to the WebService::HashiCorp::Vault object) to %args
(the backend constructor argument hash). The logger and the log_method attributes
are not passed. Why?

@djzort
Copy link
Owner

djzort commented Nov 29, 2022

It's almost certainly a bug. The Pod notes that this module is a Beta :)

Pull requests are gladly welcomed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants