-
-
Notifications
You must be signed in to change notification settings - Fork 30
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 set value for key_algorithm
for tls_cert_request
resource
#49
Comments
Facing same issue since yesterday
|
Hi ppl! |
@sandy2008 apart from the read-only attribute there is this issue
Does it work for you? |
I didn’t have this issue, could you submit a PR to my upstream? I will release it. |
Please ignore my issue mentioned above. Adding the provider regions solved the issue. |
Got it ;)
2022年8月2日(火) 21:22 Renil ***@***.***>:
… Please ignore my issue mentioned above. Adding the provider regions solved
the issue.
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJ4QRXKYTSO6TNUXIH43Z3VXEHHTANCNFSM54WEAQ5A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you @sandy2008 for solving certs issue and working now.
|
key_algorithm
for tls_cert_request
resource
This issue should be resolved by PR #50 Please comment if this issue is still present in the latest version of this module. |
Please comment if this is still unresolved by PR #50. |
Found a bug? Maybe our Slack Community can help.
Describe the Bug
A clear and concise description of what the bug is.
Module stopped working 22th July even upgraded with new release (same errors)
Expected Behavior
A clear and concise description of what you expected to happen.
Steps to Reproduce
Steps to reproduce the behavior:
Screenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: