Search Results for "manifest"

...If you have built software that you would like others to use, Scoop is an alternative to building an installer (like MSI or InnoSetup). You just need to compress your app to a .zip file and provide a JSON manifest that describes how to install it. Scoop downloads and manages packages in a portable way, keeping them neatly isolated in ~\scoop. It won't install files outside its home, and you can place a Scoop installation wherever you like. For terminal applications, Scoop creates shims, a kind of command-line shortcut, inside the ~\scoop\shims folder, which is accessible in the PATH. ...

pv-migrate is a CLI tool/kubectl plugin to easily migrate the contents of one Kubernetes PersistentVolumeClaim to another. On Kubernetes, if you need to rename a resource (like a Deployment) or to move it to a different namespace, you can simply create a copy of its manifest with the new namespace and/or name and apply it. However, it is not as simple with PersistentVolumeClaim resources: They are not only metadata, but they also store data in the underlying storage backend. In these cases, moving the data stored in the PVC can become a problem, making migrations more difficult.

...If you ask the API-server to give you deployments.v1.apps, and the deployment was deployed as deployments.v1beta1.extensions, the API-server will quite happily convert the API version and return a manifest with apps/v1. This is fairly well outlined in the discussion of this issue.