feat(config): add vault provider

[FrankYang0529]

ref: spinframework/spin#798, spinframework/spin#661

Content must go through a pre-merge checklist.

Pre-Merge Content Checklist

This documentation has been checked to ensure that:

• The title, template, and date` are all set
• File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
• Has passed bart check
• Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
• Headings are using Title Case
• Code blocks have the programming language set to properly highlight syntax and the proper copy directive
• Have tested with npm run test and resolved all errors

[vdice]

Thank you for this docs update!

A few grammatical suggestions while this is in draft (pending merge of spinframework/spin#798 as well)...

@flynnduism @mikkelhegn it looks like we're tracking changes to static/data.json -- does this look right to you?

[karthik2804]

@vdice We are tracking static/data.json because we need it to be updated for search indexing.

[mikkelhegn]

@FrankYang0529 can you run npm run build-index to update the search index and then commit the updated data.json file? We're fixing the PR template to include this step.

[FrankYang0529]

@FrankYang0529 can you run npm run build-index to update the search index and then commit the updated data.json file? We're fixing the PR template to include this step.

Hi @mikkelhegn, I run the command and committed it.

I have a question: how to install bart command? There is a check item in the list. Thank you!

[mikkelhegn]

Instructions are here: https://bartholomew.fermyon.dev/quickstart

[FrankYang0529]

Instructions are here: https://bartholomew.fermyon.dev/quickstart

Thanks! I also add the reference to pull_request_template.

[mikkelhegn]

I haven't tested the functionality, but I trust the instructions are ok :-)

[vdice]

Last thought: We don't yet have a good story around delineating between docs around unreleased Spin changes and docs that are valid for the most recent release (eg v0.6.0 currently). Until then, should we add a note somewhere that the vault config provider functionality is available in the canary release now and anticipated to be included in the next v0.7.0 release?

(Filed #195 around docs versioning strategy)

[FrankYang0529]

Last thought: We don't yet have a good story around delineating between docs around unreleased Spin changes and docs that are valid for the most recent release (eg v0.6.0 currently). Until then, should we add a note somewhere that the vault config provider functionality is available in the canary release now and anticipated to be included in the next v0.7.0 release?

Added a note for it. Thanks.

[vdice]

Thank you @FrankYang0529!