-
Notifications
You must be signed in to change notification settings - Fork 22
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
Fixes #10214: More consistant naming of techniques #1118
Fixes #10214: More consistant naming of techniques #1118
Conversation
Do not merge for now, still unsure about consequences of renaming categories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a GREAT change! It's going to make things so much clearer!
--> | ||
<TECHNIQUE name="APT package manager configuration"> | ||
<DESCRIPTION>This technique configure the APT package manager.</DESCRIPTION> | ||
<TECHNIQUE name="Package sources (APT)"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is actually 2 things in one: package sources (aka repos) and package manager settings. How about "Package sources and settings (APT)" ?
@@ -20,7 +20,7 @@ | |||
|
|||
--> | |||
|
|||
<TECHNIQUE name="Repository GPG Key Management for RPM / APT Systems"> | |||
<TECHNIQUE name="Package repository keys"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be "Package repository keys (RPM/APT)"
@@ -13,8 +13,8 @@ GNU General Public License for more details. | |||
You should have received a copy of the GNU General Public License | |||
along with this program. If not, see <http://www.gnu.org/licenses/>. | |||
--> | |||
<TECHNIQUE name="Zypper package manager setup"> | |||
<DESCRIPTION>This technique setups Zypper package manager.</DESCRIPTION> | |||
<TECHNIQUE name="Package manager configuration (Zypper)"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/configuration/settings/ ?
@@ -13,7 +13,7 @@ GNU General Public License for more details. | |||
You should have received a copy of the GNU General Public License | |||
along with this program. If not, see <http://www.gnu.org/licenses/>. | |||
--> | |||
<TECHNIQUE name="RUG / YaST package manager configuration (ZMD)"> | |||
<TECHNIQUE name="Package manager configuration (RUG/YaST/ZMD)"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/configuration/settings/ ?
@@ -14,7 +14,7 @@ You should have received a copy of the GNU General Public License | |||
along with this program. If not, see <http://www.gnu.org/licenses/>. | |||
--> | |||
|
|||
<TECHNIQUE name="Download a file from the shared folder"> | |||
<TECHNIQUE name="File download (from the policy server)"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be "File download (from Rudder server)". No "the", and more specific.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe even, judging by it's little brother "File download (HTTP)", maybe just "File download (Rudder)" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"File download (Rudder server)" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me.
@@ -14,8 +14,7 @@ You should have received a copy of the GNU General Public License | |||
along with this program. If not, see <http://www.gnu.org/licenses/>. | |||
--> | |||
|
|||
<!-- This technique lets user define a key-value in a file --> | |||
<TECHNIQUE name="Manage keys-values in file"> | |||
<TECHNIQUE name="File content from key-value pairs"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this title is a bit misleading. It sounds like you can pass in a dict of key-value pairs to make up a file. But actually it's a special technique to manage files that are in key-value format.
How about "File content (key/value format)"?
@@ -16,5 +16,5 @@ along with this program. If not, see <http://www.gnu.org/licenses/>. | |||
|
|||
<xml> | |||
<name>Process</name> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be renamed "Services" if possible, since the only visible technique in it is also about Services.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I talked with @fanf about renaming categories, and it seems it is not properly doable for now.
It is intended to check if all the required SSH keys are installed. | ||
--> | ||
<TECHNIQUE name="SSH keys distribution"> | ||
<TECHNIQUE name="SSH keys"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would be clearer if it's "SSH authorised keys" or "SSH user authorised keys" or "SSH authorised keys (users)"
@@ -14,7 +14,7 @@ You should have received a copy of the GNU General Public License | |||
along with this program. If not, see <http://www.gnu.org/licenses/>. | |||
--> | |||
|
|||
<TECHNIQUE name="Monitor a file or directory content"> | |||
<TECHNIQUE name="File and directory monitoring"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is close but not very evocative for those who know and deal with these concepts. How about "File integrity"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
much better
given parameters. | ||
--> | ||
<TECHNIQUE name="Fstab configuration"> | ||
<TECHNIQUE name="Mountpoints (fstab)"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's two words: "Mount points". But shouldn't this be "Filesystem mount points"? Since we act on filesystems, and mount points are the settings?
Commit modified |
8ac42f3
to
7cb6fe5
Compare
OK, merging this PR |
https://www.rudder-project.org/redmine/issues/10214