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.

Sign up for GitHub

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

Jump to bottom

[B&A] API specification #32

Open
takuro-sato opened this issue Dec 13, 2023 · 1 comment
Open

[B&A] API specification #32

takuro-sato opened this issue Dec 13, 2023 · 1 comment
Assignees
@chatterjee-priyanka @neilv-g
Labels
B&A

Comments

@takuro-sato
Copy link

takuro-sato commented Dec 13, 2023 •
edited

As we are developing support for deploying B&A services in Azure, we noticed that some APIs are not fully specified e.g.,
fields of EncryptionKey and KeyData.
Can you please clarify the format/requirements of the fields?
@takuro-sato takuro-sato changed the title [B&A] Requirement for EncryptionKey fields [B&A] API specification Dec 13, 2023
@chatterjee-priyanka chatterjee-priyanka self-assigned this Dec 14, 2023
@kapilvgit
Copy link

@neilv-g can you please clarify this? These structures are part of public APIs and we want to avoid making assumptions about the fields in these structures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chatterjee-priyanka chatterjee-priyanka

@neilv-g neilv-g

Labels
B&A
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kapilvgit @takuro-sato @chatterjee-priyanka @neilv-g