Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acceptance Criteria Checklist (DoD) #1614

Open
22 of 25 tasks
anfibiacreativa opened this issue May 14, 2024 · 3 comments
Open
22 of 25 tasks

Acceptance Criteria Checklist (DoD) #1614

anfibiacreativa opened this issue May 14, 2024 · 3 comments

Comments

@anfibiacreativa
Copy link
Member

anfibiacreativa commented May 14, 2024

The following checklist must be complete before a template is published.

Repository Management

Source code structure and conventions

  • GitHub Actions (This refers to .github/workflows/azure-dev.yml or custom workflow to run on a GitHub runner) is in place
  • DevContainer (/.devcontainer folder where applicable) configuration is in place
  • Infrastructure as code is in place (/infra folder where applicable, manifest files or code generators in the case of Aspire and similar )
  • Azure services configuration (/azure.yml file) is in place
  • Minimum coverage tests are in place

Functional requirements

  • azd up successfully provisions and deploys a functional app
  • GitHub Actions run tasks without errors
  • DevContainer has been tested locally and runs
  • Codespaces run [locally and in browser]
  • All tests pass

In the absence of e2e tests,

  • The application has been manually tested to work as per the requirement

Security requirements

When a service selected doesn't support Managed Identity, the corresponding issue must have been reported and the security considerations section in the readme, should clearly explain the alternatives.

  • Azure Key Vault is a preferred alternative

The following items are not strictly enforced but may prevent the template from being added to the gallery.

Project code follows standard structure, per language. Please check one.

  • Yes, follows standards
  • No, doesn't follow standards

Code follows recommended style guide

  • Yes, follows style guide
  • No, doesn't follow style guide
@anfibiacreativa
Copy link
Member Author

@pamelafox can you please confirm the security requirements are met and close the issue when done. Thank you!

@pamelafox
Copy link
Collaborator

Hm, we dont have a security guidelines section yet. We do have https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/productionizing.md#additional-security-measures which somewhat covers up but doesnt mention secret scanning. I guess we have to add another section to our long readme. Is that what you're doing for https://github.com/Azure-Samples/azure-search-openai-javascript ?

@mattgotteiner
Copy link
Collaborator

I get a 404 when I navigate to this link.
https://github.com/Azure-Samples/azd-template-artifacts/blob/main/SECURITY.md

Are we supposed to add our own security guidelines? I did not find a SECURITY.md file in azure-search-openai-javascript either

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants