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
`cloudera.cloud` is an Ansible collection that lets you manage your **[Cloudera Data Platform (CDP)](https://www.cloudera.com/products/cloudera-data-platform.html) Public Cloud** resources. With this collection, you can:
5
+
`cloudera.cloud` is an Ansible collection that lets you manage your **[Cloudera Platform](https://www.cloudera.com/products/cloudera-data-platform.html)on cloud (Public Cloud)** resources. With this collection, you can:
6
6
7
7
* Create and manage [Datalakes](https://www.cloudera.com/products/open-data-lakehouse.html) and Environments.
8
8
* Manage Users and Groups.
@@ -18,14 +18,12 @@ If you have any questions, want to chat about the collection's capabilities and
18
18
19
19
## Quickstart
20
20
21
+
See the [API documentation](https://cloudera-labs.github.io/cloudera.cloud/) for details for each plugin and role within the collection.
22
+
21
23
1.[Install the collection](#installation)
22
24
2.[Install the requirements](#requirements)
23
25
3.[Use the collection](#using-the-collection)
24
26
25
-
## API
26
-
27
-
See the [API documentation](https://cloudera-labs.github.io/cloudera.cloud/) for details for each plugin and role within the collection.
28
-
29
27
## Roadmap
30
28
31
29
If you want to see what we are working on or have pending, check out:
@@ -42,12 +40,16 @@ For more information on how to get involved with the `cloudera.cloud` Ansible co
42
40
43
41
## Installation
44
42
45
-
To install the `cloudera.cloud` collection, you have several options. Please note that we have not yet published this collection to the public Ansible Galaxy server, so you cannot install it via direct namespace, rather you must specify by Git project and (optionally) branch.
43
+
To install the `cloudera.cloud` collection, you have several options.
46
44
47
-
### Option #1: Install from GitHub
45
+
The preferred method is to install via Ansible Galaxy; in your `requirements.yml` file, add the following:
46
+
47
+
```yaml
48
+
collections:
49
+
- name: cloudera.cloud
50
+
```
48
51
49
-
Create or edit your `requirements.yml` file in your project with the
50
-
following:
52
+
If you want to install from GitHub, add to your `requirements.yml` file the following:
See [Building the Collection](#building-the-collection) for details on creating a local tarball.
81
-
82
-
## Requirements
83
-
84
-
`cloudera.cloud` expects `ansible-core>=2.10`.
85
-
86
-
The collection also requires the following Python libraries install to operate its modules:
87
-
88
-
*[`cdpy`](https://github.com/cloudera-labs/cdpy)
89
-
90
-
The collection's Python dependencies alone, _not_ the required Python libraries of its collection dependencies, are in `requirements.txt`.
91
-
92
79
`ansible-builder`can discover and install all Python dependencies - current collection and dependencies - if you wish to use that application to construct your environment. Otherwise, you will need to read each collection and role dependency and follow its installation instructions.
93
80
94
81
See the [Collection Metadata](https://ansible.readthedocs.io/projects/builder/en/latest/collection_metadata/) section for further details on how to install (and manage) collection dependencies.
@@ -116,65 +103,46 @@ For example, here we use the
116
103
var: output
117
104
```
118
105
> [!IMPORTANT]
119
-
> The CDP modules expect standard CDP authentication configurations, e.g. `CDP_PROFILE`, as described by the *Configuring* section of [CDP CLI/SDK](https://github.com/cloudera/cdpcli#configuring).
106
+
> The collection expects standard Cloudera Platform authentication configurations, e.g. `CDP_PROFILE`, as described by the *Configuring* section of [CDP CLI/SDK](https://github.com/cloudera/cdpcli#configuring).
120
107
121
-
## Building and Developing the Collection
108
+
## Building the API Documentation
122
109
123
-
To develop the collection -- additions, updates, bugfixes, etc. -- or to build resources from the collections -- API documentation, etc. -- you must first install [Hatch](https://hatch.pypa.io/latest/) according to your specific development environment.
110
+
To create a local copy of the API documentation, first make sure the collection is in your `ANSIBLE_COLLECTIONS_PATH`.
124
111
125
112
```bash
126
-
# As a Python application
127
-
pip install hatch
128
-
129
-
# With Brew (OSX)
130
-
brew install hatch
131
-
132
-
# On Fedora
133
-
sudo dnf install hatch
113
+
hatch run docs:build
134
114
```
135
115
136
-
### Developing Collection Resources
116
+
Your local documentation will be found at `docsbuild/build/html`.
137
117
138
-
To set up a development environment, you can first use the following to install the Python dependencies:
118
+
You can also lint the documentation with the following command:
139
119
140
120
```bash
141
-
hatch shell
121
+
hatch run docs:lint
142
122
```
143
123
144
-
This will create a `hatch`-managed virtual environment. (You can also associate this Python environment with your IDE, like VSCode!)
124
+
## Preparing a New Version
145
125
146
-
> [!TIP]
147
-
> You also need to ensure the collection's project directory is in your `ANSIBLE_COLLECTIONS_PATH` variable.
148
-
149
-
While you develop and work on collection resources, you can easily execute checks and linters with the following command:
126
+
To prepare a version release, first set the following variables for `antsichaut`:
This script will run a number of `pre-commit` hooks, including `ansible-lint`, as well as lint any API documentation, guides, and other resources.
156
-
157
-
If you wish to contribute your changes, please check out the instructions in the [CONTRIBUTING](./CONTRIBUTING.md) guide.
158
-
159
-
### Building the API Documentation
160
-
161
-
To create a local copy of the API documentation, first make sure the project, i.e. the collection, is in your `ANSIBLE_COLLECTIONS_PATH`. Then run the following:
132
+
Update the collection version using [`hatch version`](https://hatch.pypa.io/latest/version/). For example, to increment to the next _minor_ release:
162
133
163
134
```bash
164
-
hatch run docs:build
135
+
hatch version minor
165
136
```
166
137
167
-
Your local documentation will be found at `docsbuild/build/html`.
168
-
169
-
170
-
### Building the Collection Bundle
171
-
172
-
To create a local collection tarball, run:
138
+
Then update the changelog to query the pull requests since the last release.
173
139
174
140
```bash
175
-
ansible-galaxy collection build
141
+
hatch run docs:changelog
176
142
```
177
143
144
+
You can then examine (and update if needed) the resulting `changelog.yaml` and `CHANGELOG.rst` files before committing to the release branch.
0 commit comments