I was checking this documentation
https://docs.ansible.com/ansible/latest/user_guide/intro_dynamic_inventory.html#inventory-script-example-aws-ec2
and found that EC2 dynamic inventory is not available in github repo and other inventories are also not available.
https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/ec2.py
There is no information in Ansible release notes or anywhere. Even looks like documentation is also not up-to-date. Please share if anyone has any information about this.
Yes, official documentation is not updated and the links are resulting in 404.
I just checked official Ansible repository on Github and found that required folder is not present in "devel" branch.
However, you can still get the required ec2.py and ec2.ini files from "stable" branches.
https://github.com/ansible/ansible/blob/stable-2.9/contrib/inventory/ec2.ini
https://github.com/ansible/ansible/blob/stable-2.9/contrib/inventory/ec2.py
This is a new inventory repo
https://github.com/ansible-collections/community.general/tree/main/scripts/inventory
see oficial documentation
https://docs.ansible.com/ansible/latest/user_guide/intro_dynamic_inventory.html#other-inventory-scripts
Related
I want to clone ELK8 integrations repository into a local server and modify a few of them to remove some of their inputs. Would anyone please guide me step by step what I should do? In details, I would like to know
Where in the codes below should I change and How to build them?
https://github.com/elastic/integrations
Should I also clone and change Elasticsearch Package Repository codes?
https://github.com/elastic/package-registry
How to route kibana to get integrations list from the cloned repository?
I had tried to use CircleCI to run some tests on my spring project.I have added the config.yml as required, but since I found some of my builds fails. I delete the config.yml and unfollow the git repository to use a different template for the config.yml. But, now CircleCI won’t detect the new .circleci directory even though it is on the GitHub repository. .circleci on GitHub
This concerns an incident with CircleCI, as can be found on their website:
And on their Twitter channel:
So UI requests were temporarily disabled, but the issue has been resolved a few hours later.
On my AWX System I've configure collection in requirement.yml and all is fine.
Now, I need to insert another collection providing by Automation Hub. That's means the source is in another place. I've read this document Downloading a collection from Automation Hub but unfortunately it doesn't run. I've create an ansible.cfg in my role directory but perhaps it is not the right way.
By AWX is not possibly to configure it through WebUI like Ansible Tower.
As anyone any idea how to resolve this?
Where's define the ansible.cfg by AWX and is it possible to configure many?
Best regards,
H.
Our organization has a locally running instance of Artifactory, and also a local instance of Bitbucket. We are trying to get them to play well together so that Artifactory can serve up our private PHP packages right out of Bitbucket.
Specifically, we'd like to create a Composer Remote Repository in Artifactory that serves up our private PHP packages, where those packages are sourced from git repositories on our local Bitbucket server.
Note that we'd rather not create and upload our own package zip files for each new package version, as suggested here. Ideally, we just want to be able to commit changes to a PHP package in BitBucket, tag those changes as a new package version, and have that new version be automatically picked up and served by Artifactory.
The Artifactory Composer documentation suggests that this is possible:
A Composer remote repository in Artifactory can proxy packagist.org
and other Artifactory Composer repositories for index files, and
version control systems such as GitHub or BitBucket, or local
Composer repositories in other Artifactory instances for binaries.
We've spent a lot of time trying making this work, but haven't been able to do it. The Remote Repository that we create always remains empty, no matter what we do. Can anyone offer an example to help, or even just confirm that what we're attempting isn't possible?
For reference, we've been trying to find the right settings to put into this setup page:
Thanks!
Artifactory won't download and pack the sources for you, it expects to find binary artifacts.
The mention of source control in the documentation refers to downloading the archives from source control systems, either uploaded there as archives (don't do that), or packed by the source control system on download request (that is what you are looking for).
You can use this REST API to download automatically generated zips from BitBucket. If you can configure the composer client to look for the packages in the right place, you're all set.
Does anyone know where I can find a downloadable manual (any format) for elasticsearch? http://www.elasticsearch.org/guide/ is OK, but sometimes the site is not reachable, and searching for content is not practical.
Not that I am aware of. You can fork and run the site locally if you have problems with it not being reachable which btw never happens for me. It is available on github: https://github.com/elastic/elasticsearch/tree/master/docs
Cloning the repo is useless. You cannot build their docs since the asciidoc files for the build --all command are access protected.
The only solution is to crawl their site, for example with wget:
wget -r -l1 --page-requisites -N --convert-links -E robots=off "https://www.elastic.co/guide/en/elasticsearch/reference/6.5/index.html"
the index.html contains all the links of the doc subdirectories, so you can specify -l1 which will make wget crawl only one level deep
note that you cannot use the search function on crawled docs since there is no server running in the background
Semi related and perhaps helpful - ES docs are available as a DocSet for the Dash MacOS and iOS app for offline docs. May or may not be useful but I find it great for travel. It cost $ but can be used for free as well.
Here is the GitHub repo for all the documentation for their products:
https://github.com/elastic/docs
Please note the following disclaimer in the repo:
Conditions of use
This documentation build process is provided to the public purely for the
purpose of testing documentation changes before submitting pull requests to
the appropriate Elasticsearch repository.
The documents produced by this build process may be published only on
http://www.elastic.co. They may not be published in any other form or on
any other website without explicit permission.