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 was archived by the owner on Jan 31, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+7-34Lines changed: 7 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,23 +57,11 @@ Finally, if you need to install a dev only dependency, use:
57
57
58
58
### Running
59
59
60
-
Before running, you must have set and exported the following environment variables so houndigrade can talk to Amazon SQS to share its results:
60
+
Before running, you must have set and exported the following environment variables so houndigrade can talk to Amazon S3 to share its results:
61
61
62
-
- `QUEUE_CONNECTION_URL`
63
-
- `AWS_SQS_QUEUE_NAME_PREFIX`
62
+
- `RESULTS_BUCKET_NAME`
64
63
65
-
`AWS_SQS_QUEUE_NAME_PREFIX` should match what you use when running cloudigrade, and that is probably `${USER}-`.
66
-
67
-
`QUEUE_CONNECTION_URL` must be a well-formed SQS URL that includes your Amazon SQS access key and secret key. Many Amazon keys have URL-unfriendly characters. You may want to use a small helper script like this to generate a valid URL:
`RESULTS_BUCKET_NAME` should match the bucket name in which you want your results, the rest of the credentials are gathered from the environment.
77
65
78
66
To run houndigrade locally against minimal test disk images, follow these steps:
79
67
@@ -131,34 +119,19 @@ If you wish to run a higher-level suite of integration tests, see
131
119
132
120
### Manually running in AWS
133
121
134
-
If you want to manually run houndigrade in AWS so that you can watch its output in real-time, you can *simulate* how the cloudigrade ECS task runs houndigrade by SSH-ing to an EC2 instance (running an ECS AMI) and running Docker with the arguments that would be used in the ECS task definition. For example:
122
+
If you want to manually run houndigrade in AWS so that you can watch its output in real-time, you can *simulate* how the cloudigrade CloudInit task runs houndigrade by SSH-ing to an EC2 instance (running an ECS AMI) and running Docker with the arguments that would be used in the CloudInit task definition. For example:
You will need to set appropriate values for the `-e` variables passed into the environment, each of the `-t` arguments that define the inspection targets, and the specific version of the houndigrade image you wish to use. When you attach volumes in AWS, you can define the device paths they'll use, and they should match your target arguments here. Alternatively, you can describe the running EC2 instance to get the device paths.
152
134
153
135
# Releasing Houndigrade
154
136
155
-
Releasing houndigrade is a simple process of tagging a new version in GitHub.
156
-
157
-
1. Navigate to the [releases page](https://github.com/cloudigrade/houndigrade/releases)
158
-
2. Draft a new release
159
-
3. Check the [Pull Requests page](https://github.com/cloudigrade/houndigrade/pulls) to see all the new changes since the last release
160
-
4. For Tag Version we use [Semantic Versioning](https://semver.org/)
161
-
5. For the main release body, please include merged PRs that will be part of this release, ideally linking to the PR itself.
162
-
6. Press button, receive release. The [tag github actions workflow](https://github.com/cloudigrade/houndigrade/blob/master/.github/workflows/tag.yml) will test, build, tag, and get the image copied to quay.
163
-
164
-
You will find your image in both the [Github Container Registry](https://github.com/orgs/cloudigrade/packages/container/package/houndigrade) and in [Quay.io](https://quay.io/repository/cloudservices/houndigrade)
137
+
Please refer to the [wiki](https://github.com/cloudigrade/houndigrade/wiki/Releasing-Houndigrade).
0 commit comments