Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Allow Configuration of Azure Secret Engine, including WIF for enterprise users #29047
Allow Configuration of Azure Secret Engine, including WIF for enterprise users #29047
Changes from all commits
5406005
1c5f84b
722d336
f419421
4d18969
2a09113
e9c7872
10c2a3f
06cd28c
2ab3ba2
4ffb87d
41c6a00
0c7fcdb
7f92777
5ab7a19
dcd1195
16715c6
1131f00
1442b4a
9b8fe6e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Since this is reused in AWS curious why we didn't make a shared component?
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.
GCP, AWS and Azure will all have some small overlap because we're adding this "Access Type" option to enterprise views. However, they are some differences, specifically the group values that relate back to these engine's models.
My preference was to keep all configuration code separate in each engines own configuration file. The win for sharing this chunk of code didn't feel significant enough to introduce a shared component that would have to work around each engine's specific "group" or labeling.
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.
🎉 typescript 🎉 😍
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.
You'll see tests coverage for 'modelAttrChanged' and 'issuerAttrChanged' getters in
azure-configuration-test
acceptance test.clientSecret
.issuer
attribute changes.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.
FWIW I don't think this would happen if you didn't create a new record, and reused the record from
queryRecord
. But I'm not 💯 sureThere 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.
Historically I've run into some funky ember data stuff with
changedAttributes()
andhasDirtyAttributes
so we'll want to make sure there's ample test coverage around this logic!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.
Note: we've discussed as a team modifying this workflow. I have that as a nice-to-have ticket as I'll also need to keep the flow in-sync with AWS configuration.
I've added lots of test coverage for all the possible flows.
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.
great comment!
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.
since the
clientSecret
isn't returned by the API...does saving it completely wipe it out? Wondering if we'll need to perform a patch here on edit instead..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.
I did a bunch of testing and this doesn't seem to happen, but not because it shouldn't happen. It's not happening because the record holds onto the clientSecret. I'll revisit this when I have a fresh brain, but I probably need to unload the record on transition and then solve for this.
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.
Hmm 🤔 So when editing a config (not
clientSecret
) and then save as long as there is noclientSecret
sent in the payload then that should be fine. I know sometimes the JSON serializer automatically removes empty values and doesn't include them in the payload, so that may be working to our advantage here.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.
I'll make sure there is test coverage here to confirm my smoke testing