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

Switch JSON policy schema from using arrays to maps #1154

Merged
merged 1 commit into from
Sep 10, 2021
Merged

Switch JSON policy schema from using arrays to maps #1154

merged 1 commit into from
Sep 10, 2021

Conversation

SeanTAllen
Copy link
Contributor

The existing array based policy doesn't work with managed HSMs query language, so, we have switched
it up to using maps instead of arrays. Map keys correspond to the array index that an entry would have.
This allows us to keep ordering.

Signed-off-by: Sean T. Allen seanallen@microsoft.com

@SeanTAllen SeanTAllen requested a review from a team as a code owner September 9, 2021 13:34
@SeanTAllen
Copy link
Contributor Author

@dcantah @anmaxvl PTAL.

@anmaxvl anmaxvl self-assigned this Sep 9, 2021
@anmaxvl
Copy link
Contributor

anmaxvl commented Sep 9, 2021

@dcantah @msscotb PTAL

@SeanTAllen SeanTAllen changed the title Switch JSON polich schema from using arrays to maps Switch JSON policy schema from using arrays to maps Sep 10, 2021
The existing array based policy  doesn't work with managed HSMs query language, so, we have switched
it up to using maps instead of arrays. Map keys correspond to the array index that an entry would have.
This allows us to keep ordering.

Signed-off-by: Sean T. Allen <seanallen@microsoft.com>
Copy link
Contributor

@dcantah dcantah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. Let's make sure we circle back to the issues we opened for improvements here

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

Successfully merging this pull request may close these issues.

3 participants