C0ffeeCode/rvault
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity

updated Compliance and testing

Browse source
This commit is contained in:
someone 2024-06-02 21:11:07 +02:00 committed by C0ffeeCode
parent 480d4f7e3d
commit 8f358517e5
Signed by: C0ffeeCode
SSH key fingerprint: SHA256:prvFOyBjButRypyXm7X8lbbCkly2Dq1PF7e/mrsPVjw
3 changed files with 14 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
chapters/05-API-Compliance-and-Testing.typ
View file

@ -1,2 +1,14 @@
= API-Compliance and Testing = API-Compliance and Testing
One of the goals of this implementation is to provide compatability to the current version of the vault written in Go.
Therefore, a go client is used for testing.
To ensure compatability, the openapi specification published by HashiCorp is used as a reference. It provides information on input parameters, types and return values.
Implemented tests are:
- Write a secret
- Destroy specific versions of a secret
- Read a secret
- Read a metadata entry
- Write a metadata entry

2
chapters/architecture/Dynamic-Routing.typ
View file

@ -3,7 +3,7 @@
This issue has previously been adressed as "dynamic routing". This issue has previously been adressed as "dynamic routing".
Problem can be split in two, // TODO // Problem can be split in two, // TODO
In Axum, routers can be configured using a fluid-like API #footnote[Term borrowed from C\# and OOP]. In Axum, routers can be configured using a fluid-like API #footnote[Term borrowed from C\# and OOP].

2
rvault_description.txt
View file

@ -15,4 +15,4 @@ Achieved features include:
- Design of the architecture - Design of the architecture
- Implementation of dynamic routing to allow for exchangeable secret engines - Implementation of dynamic routing to allow for exchangeable secret engines
- Basic kv-store examples - Basic kv-store