Are preinit/postinit supported anymore?

[TWolversonReply]

An old issue refers to preinit, but only in the context of removing it from the documentation, as does this test but otherwise it looks like neither are supported (anymore?)

I would like to be able to use preinit/postinit hooks to customise the one-time setup of a repo based on a sample that I publish, such as asking the user a number of setup questions that will then edit the files copied in by azd init. Is this kind of workflow supported or anticipated to be in the future?

• the postinit task might include removing itself, so that the resulting solution setup is unpolluted by concerns that relate purely to 'vending' the sample code and aren't relevant thereafter

[rajeshkamal5050]

@wbreza it this even supported?

[wbreza]

You are correct - the preinit hook is no longer supported. Since the azd init command itself is used to download and initialize a template it would have inconsistent behavior depending on whether the -t template argument is specified, and whether the user already have the project downloaded locally.

Could you explain your scenario in a more detail so we can figure out next steps and see how it fits in with future scenarios on our roadmap?