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

[Feature] Should accommodate volatile plugin data #2

Open
smougenot opened this issue Dec 23, 2023 · 0 comments
Open

[Feature] Should accommodate volatile plugin data #2

smougenot opened this issue Dec 23, 2023 · 0 comments

Comments

@smougenot
Copy link

First, thank you for this code. It worked great for me.

Limitation encountered

It looks like this role does not handle plugin data change (secret refresh).

Feature

This feature aims to manage volatile secrets in the plugin data.
Because often the credential data are ephemeral.

Use case to reproduce

(First use of the role works fine)

  • setup pve_acme_plugin_data content
    • for my dns provider api (OVH) generated secrets may be valid only one hour.
  • run the playbook
    • worked fine
  • wait for expiration
  • try refresh
    • the api cal fails (indeed because of expired secrets)
  • renew secrets from dns provider
  • update pve_acme_plugin_data content
  • try refresh
    • the api cal fails again
    • the acme plugin was not update with the new cerdential

possible workaround

A quick work around could be to change the value of pve_acme_plugin_name.
I did not tried.

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

1 participant