I cannot for the life of me find out where this is happening, otherwise I would offer a patch, but I am trying to save a platform node without triggering verification.

This works for the platform if I specify $node->no_verify = TRUE; . However, it will still create verify tasks for the site.

The site verification should respect the original no_verify, I think...

If someone can help me find the source of this and can point it out I would love to submit a patch.

Comments

omega8cc’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Maybe I have missed something (you didn't provide enough context) but normally the Save must be followed by Verify or things will get wild fast. You probably modified something heavily enough, because stock Aegir never runs Verify for Sites when Platform is verified, so there is no reason to try to Save Platform node without running Verify on it. You should rather investigate why and how you got to the point where running Platform verify triggers Sites Verify. Something like this happens only for Platforms when you Save/Verify the Server node - it triggers Verify for all Platforms (but never for Sites). If you are trying to achieve some non-standard workflow, note that there is also something like $site->no_verify = true; or $task->ref->no_verify = TRUE; used in the code, depending on the context.

At least, this is partially wrong: https://twitter.com/thinkdropNYC/status/297371193298780162

#aegir #drupal #tip: When you Verify a platform, it will schedule a Verify of each of it's sites. Verify a site does NOT verify a platform!

Only that part "Verify a site does NOT verify a platform" is obviously correct.

jon pugh’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

yep, I just tracked this back to my own code. a teammate had put this in our system and I hadn't noticed!