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

docs: update README for artifact coordinates, correct configuration properties, tighten style #175

Merged

Conversation

timothystone-knsl
Copy link
Contributor

@timothystone-knsl timothystone-knsl commented May 28, 2024

The README referenced the old Maven coordinate for the AWS KMS. Update to the new coordinate and add some additional best practices in Maven such as the use of versions in properties. In code fences, add a syntax hint.

Unify the use of YAML mappings over "property" style keys, c.f., spring.cloud.aws. Where keys used camelCase, correct and use kebab-case for Spring recognition. Apply inline code style where needed, e.g., {cipher}. Use a single form of the YAML file extension, c.f., "yml" vs. "yaml".

Fixes #177

…roperties, tighten style

The README referenced the old Maven coordinate for the AWS KMS. Update to the new coordinate and add
some additional best practices in Maven such as the use of versions in `properties`. In code fences,
add a syntax hint.

Unify the use of YAML mappings over "property" style keys, c.f., spring.cloud.aws. Where keys used
camelCase, correct and use kebab-case for Spring recognition. Apply inline code style where needed,
e.g., `{cipher}`.  Use common YAML file extension, c.f., "yml" vs. "yaml".

Signed-off-by: Timothy Stone <[email protected]>
@timothystone-knsl timothystone-knsl force-pushed the docs/fix-artifact-coordinate branch from ec65728 to 29cf46a Compare May 28, 2024 18:32

e.g. `application.yml`
If all cipher values of your application have been encrypted with the same KMS key and algorithm, you can configure
the `keyId` and `encryptionAlgorithm` globally in the `bootstrap.yml` as shown above. In case you have to decrypt
Copy link
Contributor Author

@timothystone-knsl timothystone-knsl May 28, 2024

Choose a reason for hiding this comment

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

The use of keyId and encryptionAlgorithm here were left as I was not certain how the "extra options" might be defined in the YAML, i.e., should the form be kebab-case or camelCase?

@danielrohe
Copy link
Member

👍

1 similar comment
@oussewa
Copy link
Member

oussewa commented Jun 7, 2024

👍

@oussewa oussewa merged commit 8b284ed into zalando:master Jun 7, 2024
4 checks passed
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.

README formating and incorrect artifact coordinates
3 participants