Adam Wójcik

> Hi @Adam-it, looks fantastic, I'm reading through it now. > > About the `--overwrite` option: is that really necessary? It seems to me that when you deploy an application...

> > About the certificate base64 string: wouldn't it be better if we used a secure file in the DevOps library for this? It is more secure and also easier...

> > secure file is 'problematic' as it may not be an input in the flow itself. Here the user would always need to create a variable group > >...

> Sure, he may need to, but he'll need to go to DevOps anyway, as the pipeline needs to be created, based on the definition. Also: it's not either/or, we...

@martinlingstuyl I removed the overwrite parameter and added this as default in the script. I also added `CertificateSecureFileId` var in the yaml file and info that we should specify in...

> Are we already set on the acronym `azdo`? I'm personally not a fan of this as it doesn't feel right for Azure DevOps 😅 Internally we use AZDO when...

> Something like `m365 spfx project devops pipeline add` would be more clear indeed. isn't devops a bit to general? It does not necessarily mean Azure DevOps. I think DevOps...

> Everyone I know calls it just DevOps 🤷 You can say the same about our `flow` section. Flow is also very abstract because it actually stands for workflow instead...

ouch sorry @milanholemans I think I misclicked somewhere and edited your post 🙏 > Yes, but for new people that never knew Microsoft Flow, it's weird. But don't we consider...

@pnp/cli-for-microsoft-365-maintainers what do you think? Is `DevOps` good enough so that most of devs will recognize it as `Azure DevOps` and it will be clear that `m365 spfx project devops...