-
Notifications
You must be signed in to change notification settings - Fork 102
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
Unable to retrieve secret value #947
Comments
This issue is marked as incomplete because it has been open 30 days with no activity. Please remove incomplete label or comment or this will be closed in 5 days. |
@cderici This issue was automatically marked as incomplete. Is there any effort placed on implementing what is required here? |
Sorry for the late response, Guillaume, I do have an active ticket for this, I'll take a look very soon. Though keep in mind, the support for the secrets are pretty rudimentary at this point (on libjuju), only some basic stuff that Juan implemented to enable people to use it a little bit. We'll have a proper roadmap item to bring full support of secrets in the next cycle to both pylibjuju and the terraform provider. |
This issue is marked as incomplete because it has been open 30 days with no activity. Please remove incomplete label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
@cderici is there any news on this issue? Unblocked myself by using the facade directly: await f.ListSecrets(filter_={"uri": pk_id}, show_secrets=True) |
#1065 #### Description ListSecrets facade takes 2 arguments: `filter_`, and `show_secrets`. Previous instanciation passed a dict, which then landed in `filter_` field. Fixes: #947 #### QA Steps *<Commands / tests / steps to run to verify that the change works:>* await f.ListSecrets(filter_={"uri": <secret_id>}, show_secrets=True) All CI tests need to pass. *<Please note that most likely an additional test will be required by the reviewers for any change that's not a one liner to land.>* #### Notes & Discussion *<Additional notes for the reviewers if needed. Please delete section if not applicable.>*
@cderici we are also affected by this issue. Is there any way we can track progress? |
We recommend using @gboutry's (fairly simple) workaround of using Instead, for new charm integration tests moving forward, we're focussing our efforts on https://github.com/canonical/jubilant -- which is far too alpha to use right now, but just letting you know the direction. Our intention with that is to have an alpha version to try by the end of Jan, and a v1 to use by the end of the 25.04 cycle. |
This is supposed to be fixed since 3.5.2.0: #1071 |
Okay, I hadn't read carefully and presumed it would require a new feature. I'll reopen, and we can look into this after the Christmas break -- if it's a straight-forward bug in python-libjuju we'll try to fix it, if it requires new wiring or a new feature, we'll probably skip. Note that Charm Tech agreed to take over maintenance of python-libjuju from the Juju team as they didn't have time with the Juju Mongo-to-dqlite transition, but Charm Tech also has our own roadmap items. :-) For reference: |
@james-garner-canonical Assigning to you to look at after the break. Let's determine the cause of this, and if it's a straight-forward bug fix we should go ahead and fix it. |
Description
I am unable to retrieve the Juju secret content. I'm not certain whether this is a real bug or whether "I'm holding it wrong". In any case I haven't found how this can be done by looking at the documentation.
Whenever I try to retrieve the juju secret value, I receive "None" even though I know the secret exists and has some content (via the CLI).
Urgency
Blocker for our release
Python-libjuju version
3.2.2
Juju version
3.1.5
Reproduce / Test
Here's how I am using the lib:
And the results I'm getting:
On the other hand, I am able to get the secret via the Juju CLI
The text was updated successfully, but these errors were encountered: