Owner: Architect:

Francesco Ilario

Story (Required)

As a Primaza user, I will like to be able to determine how my data gets projected into application so that I can consume SEDs in the format that my application already understands.

Background (Required)

Today Primaza only support projection of SEDs into the application via volume mount of a secret where each field of the secret becomes a file where name of file is the key and the content of the file is value. This approach is fine if application support Service Binding specification. However if we want to support more projection methods that better match what applications expects we should support at least Json and Yaml file formats for the SED key/value list.

Glossary

Formatter: A mechanism to project SEDs in different formats.

Out of scope

• Go Template Format
• JSON/YAML Mappers

In Scope

Json and Yaml formats

Approach(Required)

Instead of sending an SED represented as a secret that gets mounted resulting of multiple files per key, we can send a secret with a single key being the file name and the value being a base64 encoded blob with the specified format containing key/value list for the SED. The mounting will happen exactly as it happens now but the result inside the container will be a single file instead of multiple files. See discussion 200 for ideas on how to implement.

Demo requirements(Required)

A great demo will be showing a service claim showing json format and another claim showing Yaml format. The Service Binding projection should still work as before.

Dependencies

NA

Edge Case

NA

Acceptance Criteria

Formatter support Json and Yaml in addition to Service Binding
New test for Json format
New test for Yaml format
Documentation on how to add formatter section in claim CR

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied