nofar
nofar
I'm unclear on what exactly isn't working and what we're trying to fix with these changes. Additionally, I'm not sure where the new methods are being used.
> In the AnsibleVariable model, _hidden_value_ returns a series of asterisks, while _hidden_value?_ returns a boolean. The author's intention was to delegate **hidden_value?**, but this led to an illegal field...
I'm getting the following error when navigating to the `Variables` tab: ``` RuntimeError (Failed to implement AnsibleVariable.hiddenValue, tried: - `Types::OverridenAnsibleVariable#hidden_value`, which did not exist - `Presenters::OverridenAnsibleVariablePresenter#hidden_value`, which did not exist...
> @nofaralfasi I think that is because you still have the broken GQL scheme... Did you make sure the content of #716 is present on your branch? You are right,...
> Glad you got it sorted. Yes, the value may indeed still be extracted from the query response. I suppose we could check if the user has the `edit_ansible_variables` permission...
> FYI, I think this same issue is affecting the ansible inventory report in Foreman that is used for ansible/AWX to use Foreman as an inventory source. Previously any hidden...