I'm not the author of this change, and honestly don't even know the
whole story behind why it changed. But since this is causing a lot of
The syntax to push an image with aeolus-image has changed. Here is
the new syntax:
$ aeolus-image push --provider ec2-us-east-1 --account matt_ec2 \
--image 6ae8421f-9ab2-4925-8f8d-ab165862b137 \
--build bf2c3ef3-2d67-455c-9c19-0d9a6bb9bdbb \
I have documented this on the
page as well.
Hello aeolus community,
In preparation for the upcoming community release 0.5.0 of aeolus, I am removing the old 0.2.0 directory.
I have archived it; on the off-chance that anyone needs anything from that directory, please contact me directly and I can point you at the archive.
After talking a bit to Mo, we decided it might make more sense if we wrote out an oauth.json file that aeolus-configure could parse. This does two things:
- Developers can just run the rake task and have a configuration file generated locally. (They will still need to configure iwhd and Factory to *use* this configuration on their own.)
- The file is only generated if it's missing, which means that it won't get overwritten. This allows aeolus-configure to simply take the keys from this file and use them to configure other components.
This is related to https://bugzilla.redhat.com/show_bug.cgi?id=749254 though it doesn't directly solve it. There's another half of this which needs to be done in aeolus-configure. Right now, we write a config file that doesn't correspond to what iwhd and Factory use, so this will actually break things until the aeolus-configure part is implemented. But I want to get someone to look this over and confirm that this is a good strategy overall.
A number of folks have raised concerns about the state of the general
aeolus conductor & configure backlogs. It has been quite a while since
anyone has groomed the backlog or the unassigned stories and it is very
difficult to see where we currently stand.
I'll start clearing things out at 1PM EST if no one raises an objection
before and then start filling in stories that we know are needed to get
the project to a compelling 1.0.
Thanks in advance,