-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Added keys to output for cog service account #2825
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @JimPaine,
Thank you for the enhancement! It is a bit weird for it to be key1 and key2, what does the portal say? I think we should align most closely with that over the API.
We should add a check to the tests to ensure the properties are set:
resource.TestCheckResourceAttrSet(resourceName, "key1"),
Also could we add these new properties to the documentation?
Hi @katbyte It is also in the portal as key1 and key2 so while it may seem a little odd it is probably best to keep it aligned? I will work on the requested changes so thanks for the feedback. |
Co-Authored-By: JimPaine <jim@jimpaine.io>
Co-Authored-By: JimPaine <jim@jimpaine.io>
Co-Authored-By: JimPaine <jim@jimpaine.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested changes made and I have also commented on the points around what to do when we fail to get the keys, agreed with the thoughts and have wrapped up the err rather than removing the resource.
Tests and documents updated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey @JimPaine
Thanks for this PR :)
I've taken a look through and whilst this LGTM I've got some questions around the naming of the fields - I believe it'd be better to match the naming of the other resources; what do you think?
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tombuildsstuff Updated keys to match terraform naming rather than the API, ensuring a consistency between documentation and resources.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey @JimPaine
Thanks for pushing those changes - there's a couple of minor docs phasing changes which could make more sense upon reflection (which I'm going to push a commit for) but this otherwise LGTM 👍
Thanks!
dismissing since changes have been pushed
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
When creating a cognitive service account the keys were not returned so you were unable to configure downstream services.
Related Issue #2567
Key things to note:
(fixes #2567)