Skip to content
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

the readme contains no information regarding galaxy-install method #17

Closed
ssbarnea opened this issue Feb 22, 2016 · 0 comments
Closed
Milestone

Comments

@ssbarnea
Copy link

README file contains no information regarding galaxy-install method

Please just update it in order to include

ansible-galaxy install Datadog.datadog
@olivielpeau olivielpeau added this to the 1.0 milestone Mar 23, 2016
DavidWittman added a commit to DavidWittman/ansible-datadog that referenced this issue Apr 26, 2016
tmcevoy14 referenced this issue in udemy/ansible-datadog Mar 29, 2017
added info

move api key to defaults

Add real username

Change order

install latest datadog-agent release

These changes are required to install the latest 5.0 release of the agent that is not affected by POODLE.
I had to swtich to ``stable``. I'm not sure why the latest release is not on ``unstable``.

Initial Redhat Support

fixed apt usage in redhat

add release appropriate psutils

tested on centos 5.x

psutil is included with the 'omnibus' install of the agent

Add tags to the datadog config file

updated to include process checks

updated process checks to align correctly; updated readme with new process check feature

Parameterize the use_mount setting in datadog.conf

make datadog config fully parameterized

quote variables

Add template & rendering for datadog /etc/conf.d/*.yaml files

Add info about "datadog_checks" and "datadog_use_mount" to README.md

Add info about "datadog_config" to README.md

README fixes; Include null default for datadog_checks

default value for datadog_checks needs to be an empty dict

Only create /etc/dd-agent/conf.d/process.yaml when datadog_process_checks is defined

Adding enabled flag for Packer builds, preprod envs, etc

Deprecate process check separate handling

The common `datadog_checks` interface should be used instead

Add more supported OS versions to metadata

Factorize datadog.conf creation

[olivier.vielpeau@datadoghq.com] Also factorized the service task

Remove need to redefine default vars in playbook

`datadog_config` does not require `api_key`, `dd_url` and `use_mount` anymore,
the values of respectively `datadog_api_key`, `datadog_url` and `datadog_use_mount`
are used if defined.

Template YUM repo to support different archs

[olivier.vielpeau@datadoghq.com] Use `template` task instead of `copy`

Delete unused vars/

Prepare ansible galaxy release

Update README and metadata

Fix markdown formatting of author info in README

[readme] Mention that the role needs sudo rights

Related to #3

[apt] Add apt-transport-https to the debian install

In preparation for HTTPS repo.

Changed keyserver to use port 80

Changed the keyserver to utilize the supported port 80 instead of the
default 11371 for use on networks that block/firewall non-standard
ports. When specifying a port number, you need to prepend the URL with
“hkp://“.

[yum] Check signature of the agent's RPM package

For Datadog Agent 5.5.0, the RPM package is signed with a GPG key. Let's
check the validity of this key when installing the RPM package with
Ansible.

It also enables the use of HTTPS on our yum repository.

Adds explicit file permissions

This came about due to issues in the environment from which I work in.
We are bound by strict CIS rules which caused the files dropped by
ansible to have a mode of 0600 and owned by user root.  Preventing the
`dd-agent` user from reading his own config files.

This PR simply enforces that user to own his the files such that he can
read them allowing the daemon to start.

Note that this PR assumes the user is dd-agent.  While this is true for
EL, I'm unaware of what the user is for Debian packages.

Sets default user to root

* Uses an override for the red hat package

Sets default user to dd-agent

* Per recommendation set the default user to dd-agent
* I left the group as root as this would fail on the debian package
* Removes override allowing end users to customize as needed.  I simply overly thought out the solution anyways

Add a link to the role's Ansible Galaxy page in the README

Add Galaxy install to README

Closes #17

Avoids bare variables which is deprecated

[readme] Use `become: yes` instead of `sudo:yes`

`become: yes` is preferred since Ansible 1.9

[meta] Set min Ansible version to 1.6

Since we're using `keyserver` on `apt_key`

[meta] Add Xenial to supported platforms

Add Changelog, and prepare initial release

Allow apt repo settings to be set by playbook user

To enable deploys using a local apt mirror.

New variables:

 * datadog_apt_repo
 * datadog_apt_key_url

[changelog] Prepare 1.1.0 release

Adding datadog tracing to ansible-datadog

Updating config files

Adding ability to add check agents to main.yml

Adding datadock config checks to datadog role

Adding datadock config checks to datadog role

Adding hadoop and mysql steps to datadog

Fixing snake-bit issue

updating repo to default to disabled

Enable repo for datadog trace agent

Adding monitoring acceptance tests

Adding mysql

Removing datadog tracing since its bundled with latest dd-agent

Adding NTP as a default datadog check

Revert "Adding NTP as a default datadog check"

Make sure dd-trace-agent is uninstallad before installing datadog agent

Fixing - making yum instead of service

adding ssl cert expiry check files

adding ssl cert expiry check files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants