Learn more about these different git repos.
Other Git URLs
Just noticed that the Hub desctiption is being pulled from FAS now, but then can still be changed in Hubs (i assume the change does not get sent back to FAS)
IMHO, we should make a decision if we want to pull this from FAS, and if we do, update the descriptions of these groups to match better hubs, and also not let a hub owner change it in hubs.
The other option here is to not pull it from FAS at all, and just keep this value soley in hubs for the hub.
As far as I know there is no "description" field in FAS. So I'm pulling a reasonable default from the "apply_rules" field and let the hub owner change it as they see fit. Do you think I should not pull anything at all and start with an empty description?
abompard added a new comment to an issue you are following: As far as I know there is no "description" field in FAS. So I'm pulling a reasonable default from the "apply_rules" field and let the hub owner change it as they see fit. Do you think I should not pull anything at all and start with an empty description?
abompard added a new comment to an issue you are following:
After looking into the code a little bit here, I saw there was some logic to not replace a description, but on the vagrant dev instance, running sync group from fas replaces the description created by populate.py with the rules entry from FAS.
That is really the thing here that worried me, that the field is replaced every time a sync from fas is done.
Hmm, that shouldn't happen. Do you know what triggers the sync? Is it a fedmsg after a FAS change?
it happens when I run the sync group from FAS script in the / dir of the repo.
Oh yeah my bad :-)
Commit 9de37d6 fixes this issue
Login to comment on this ticket.