There are a lot of options in persistConfig that aren't mentioned in the README. We should add a section to the README that documents each option you can declare in a persistConfig.

Is your proposal related to a problem?

Currently, it seems that Thanos is requiring getting its JS script from internet:
https://github.com/thanos-io/thanos/blob/main/pkg/ui/templates/bucket.html
This is a blocking point for air-gapped K8S cluster.

Describe the solution you'd like

Provide all the necessary scripts if internet is not accessible.

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTR

Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

See https://jsfiddle.net/ygaprkbe/2/

In the console you will see {} but it should be the object in the update call.

So far I've only seen this when updating items inside of an array.

Also, most likely a related bug: https://jsfiddle.net/ygaprkbe/3/

The modifications object here is { foo.bar: 444 } which seems similar to this old bug #1195

13.2.5.55 DOCTYPE name state

EOF
Emit that DOCTYPE token

Change to "Emit the current DOCTYPE token" to match the style of the rest of the doc.

Here is an issues with detailed description: NekR/offline-plugin#77

Question

Environment:
v1.1.1
v1.20.6+k3s1

• Node config
  • Alpine (2x worker)
  • Ubuntu 20.04 (Worker/master)

Does Longhorn Require Bash?

Reason I ask is because I'd installed the following and remounted / as shared and whilst longhorn was running I couldn't get anything to mount if the pod was scheduled to the alpine node, longhorn would be showing attaching/detac

when string-ascii and string-utf8 were introduced, many functions documentation in the Clarity reference were not modified to include references to these new types when applicable (used to be a buff but I doubt many new people are aware of that).

Example of functions that can take a string (either ascii or utf8), but not the exhausti