Includes and int. snippets added #107
Conversation
AsfUser
requested review from
AlbrechtSchoenfeldGitHub,
SchettlerKoehler and
maybeec
as code owners
|
the artifact has been generated and you can find a preview of your change here: Actions - select your pull request workflow - scroll to the bottom, there you should be able to download the artifact (only works if something has been changed in solutions) |
|
|
||
| The created resources should follow a *uniform naming schema*. This requires naming to be factored out in a centralized module. Terraform supports factoring out common code in modules. However the backend must already exist and should also follow a naming convention. The recommendation is therefore to expose the common terraform module via an additional path that does not require a backend to determine the names for the azure resources representing the backend. | ||
| [.internal] | ||
| provisioning_platforms_azure_dec_opt |
There was a problem hiding this comment.
Internal snippets that are used in solutions currently must be prefixed with solution_, because of technical reasons in a synchronization action.
|
|
||
| [.internal] | ||
| solution_microservices_azure_aks_infra_detailed_native_setup | ||
| microservices_azure_aks_infra_detailed_native_setup |
There was a problem hiding this comment.
Internal snippets that are used in solutions currently must be prefixed with solution_, because of technical reasons in a synchronization action.
| |Process |Aligned processes across teams; team flexibility to customize boards, dashboards, and so on |Different processes per prj;e.g. different work item types, custom fields |same as many projects | ||
| |======================= | ||
| [.internal] | ||
| provisioning_azure_devops_struct |
There was a problem hiding this comment.
Internal snippets that are used in solutions currently must be prefixed with solution_, because of technical reasons in a synchronization action.
|
|
||
| *Recreation of resources in short intervals* might cause pipelines to fail. Even if resources are deleted they might still exist in the background (even although soft delete is not applicable). Programming languages can therefore get confused if pipelines recreate things in short intervals. Creating a new resource group can solve the problem since they are part of the tecnical resource id. | ||
| [.internal] | ||
| provisioning_azure_devops_orch |
There was a problem hiding this comment.
Internal snippets that are used in solutions currently must be prefixed with solution_, because of technical reasons in a synchronization action.
| :idprefix: | ||
| :idseparator: - | ||
|
|
||
| include::../../includes/streamproc_problem/index.asciidoc[] |
There was a problem hiding this comment.
Please do not use includes as a first content in solutions, because the solution is then named by the header in the include. That can lead to multiple solutions with the same name, when new solutions use the include in the same way.
Either change the structure of the document and the include or add a first level header above
E.g.:
= Apache Kafka on Microsoft Azure
include::../../includes/streamproc_problem/index.asciidoc[]
...
2 participants
No description provided.