-
Notifications
You must be signed in to change notification settings - Fork 74
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
Introduce "managed" object for all openwhisk entities #633
Comments
@pritidesai actually, there would be no "managed" keyword anywhere in the YAML; instead a "managed" object would appear in the annotations of OpenWhisk entities (that are managed / tracked at the server-side). This would mean, as part of this issue/design, that we would propose the structure of this object and a reserved set of keynames to use within the annotation. This annotation would automatically be appended by tooling (and perhaps stripped on export/creation of a new manifest). There may need to be a command line option to enable this feature (and/or preserve/sync/update the "managed" object annotation in the saved client-side YAML. |
@pritidesai allow me to upload today the 0.9.0 spec which has placeholders for some of the underlying use cases that are driving this feature (mainly using wskdeploy from IDEs). |
Deployments are classified into two categories: managed and unmanaged Managed Deployments: Managed deployment are the ones when OpenWhisk entities are deployed using
Every OpenWhisk entity in the manifest file will be annotated with:
Where the text OpenWhisk is a constant prefix and \0 is also constant and is the NULL character. The <size_of_manifest_file> and <contents_of_manifest_file> vary depending on the file. Managed deployments will also generate a separate manifest YAML file with all these hidden annotations in every OpenWhisk entities. Now, subsequent deployment ( OpenWhisk entities which are deployed using some other tool or automation and also appearing in the manifest file will left unmodified. Such entities are classified as external entities and will not be overwritten. Undeployment of such project can be driven with [UPDATE] Undeployment of such project can be driven with
Unmanaged Deployments: Unmanaged deployments are done without specifying Questions:
References:
|
We would like to start distinguishing
managed
vsunmanaged
deployments to ease management of deployed whisk entities. The idea is to create openwhisk entities annotated with a project name. These entities could be created with a single deployment or many different deployments. When it comes to clean up, all the entities annotated with the same project name can be deleted. This can also help listing entities which belong to one particular project.Introduce a new object
managed
at the project level withname
as a single entity for now, this will be extended to have more than just this one entity:Add this new object as a annotation to every entities in manifest/deployment file.
@mrutkows @lionelvillard please correct me if I am wrong or have incorrect explanation here.
The text was updated successfully, but these errors were encountered: