You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
Opening this ticket under Calyptos but this will most likely apply to the deployer plugin. Currently this applies to the several Chef Cookbooks which are invoked by Calyptos.
Suggesting that where possible these cookbooks/recipes/templates apply a comment to the files they generate to inform administrators that this file is being generated/edited by Calyptos (or a specific recipe, etc).
Something like:
"# This file was generated by Eucalyptus-Cookbook::helloworld on date:XX/YY/XXXX"
We've seen configuration mgmt tools (un-related to Calyptos) frustrate users when they can't figure out why the continue to lose their manual system configurations, finally to figure out they were being over-written by their own mgmt tools.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Opening this ticket under Calyptos but this will most likely apply to the deployer plugin. Currently this applies to the several Chef Cookbooks which are invoked by Calyptos.
Suggesting that where possible these cookbooks/recipes/templates apply a comment to the files they generate to inform administrators that this file is being generated/edited by Calyptos (or a specific recipe, etc).
Something like:
"# This file was generated by Eucalyptus-Cookbook::helloworld on date:XX/YY/XXXX"
We've seen configuration mgmt tools (un-related to Calyptos) frustrate users when they can't figure out why the continue to lose their manual system configurations, finally to figure out they were being over-written by their own mgmt tools.
The text was updated successfully, but these errors were encountered: