From 8eb3d2c154cda249756e7970afd1a3f14a0f7509 Mon Sep 17 00:00:00 2001 From: Ryan Lerch Date: May 27 2026 23:07:46 +0000 Subject: Update README.md --- diff --git a/README.md b/README.md index 219506e..c4d0523 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,3 @@ -# cloud-image-uploader +# MOVED TO FEDORA FORGE -An AMQP consumer that automatically uploads Cloud and container images to their respective homes. - -## Configuring - -The `fedora-messaging` service is the container entrypoint and is also used to provide most of the configuration. An example configuration file is included and the full list of options are in [fedora-messaging's configuration documentation](https://fedora-messaging.readthedocs.io/en/stable/user-guide/configuration.html). The `FEDORA_MESSAGING_CONF` environment variable should be set to the configuration file's location. - -In addition to `fedora-messaging`, the [Azure Ansible collection](https://docs.ansible.com/ansible/latest/collections/azure/azcollection/) needs Azure credentials provided. It supports using environment variables, a credentials file at `~/.azure/credentials` or the `azure-cli` credentials. For example, to authenticate via environment variables using an app registration in the Microsoft Entra ID service with a client secret, setting the `AZURE_TENANT`, `AZURE_CLIENT_ID`, and `AZURE_SECRET` along with the `AZURE_SUBSCRIPTION_ID` will be picked up by the Ansible playbook. The app registration needs to be configured in the given subscription's access control settings. - -Container image upload to registries uses the `skopeo` and `buildah` commands, so for this to work, the system must be in a state such that these commands have the necessary credentials to upload to the registries configured, non-interactively. If no container registries are configured, container images will not be handled. +https://forge.fedoraproject.org/apps/cloud-image-uploader \ No newline at end of file