List view
- No due date•0/1 issues closed
- No due date
There are a number of issues with the way ADRs work. This milestone is to improve the way ADRs work.
No due date•0/3 issues closedRight now the root modules (in particular infra/app/service and infra/app/database) contain lots of data sources. It would streamline the modules to take those data sources and move them into modules. The general idea / pattern is to reorganize modules in infra/modules to be sets of modules like so: ``` infra/modules/database/ --> infra/modules/database/resources/ infra/modules/database/data/ infra/modules/database/interface/ ``` the resources/ module would be used to create the database resources, and the data/ module would be used to reference the database resources. so the infra/app/database/ root module would call infra/modules/database/resources/ and the infra/app/service/ root module would call infra/modules/database/data/ The interface/ module is used to take over the purpose that the config modules currently play (to facilitate cross-layer dependencies). ## Relevant goal this would help to increase adoption by make future updates easier / reducing merge conflicts
No due date•5/5 issues closed- No due date•0/1 issues closed
- No due date•4/5 issues closed
Right now workspaces are per layer, but sometimes as an infrastructure engineer you want to test changes across multiple layers
No due date[OpenTelemetry](https://opentelemetry.io/) (aka "OTel") is an open-source monitoring protocol. It can collect telemetry data (logs, metrics, and traces) from an application and forward it to various viewing sources. Critical to the understanding of OpenTelemetry is knowledge of ["traces"](https://opentelemetry.io/docs/concepts/signals/traces/), which are a high-resolution time-stamped key-value data source. Used properly, traces provide more information at a higher resolution than can be provided by logs and metrics. OpenTelemetry itself, being an open protocol, can be forwarded to many different viewing frontends. Some frontends for consuming OpenTelemetry include AWS X-Ray, Datadog, New Relic, and Splunk. OpenTelemetry is generally implemented via a combination of a client library (eg. a package inside of the application), a backend sidecar (eg. a container that runs beside the application), and a viewing client (eg. AWS X-Ray, Datadog, New Relic, Splunk, etc). This milestone would involve adding all 3 of those things to our application/infrastructure and configuring the application to emit some generic traces. For the sake of the platform templates, AWS X-Ray will be our viewing client of choice, although we may also run a proof of concept showing the ability to switch between viewing clients at will. via @coilysiren
No due date•0/1 issues closed- No due date•0/1 issues closed
- No due date•0/1 issues closed
- No due date•0/2 issues closed
- No due date•2/3 issues closed
Some projects use Microsoft azure instead of Amazon web services.
No due date•1/4 issues closed- No due date•3/5 issues closed
All projects should have some sort of feature flag mechanism for separating deploys from product releases. This allows projects to move closer to continuous delivery while still providing business owners with control over when features are visible to end users. It also provides methods for more complex or multistage releases that might involve specific user groups, pilots, etc. AWS provides a service called Evidently that provides functionality to do A/B testing, more generally known as split testing. Split testing functionality is effectively a superset of feature flag functionality, so this ticket is to implement split testing support into the template. credit to @aligg and @Nava-JoshLong for this
No due date•4/5 issues closedMost projects need architecture documentation to support getting authority to operation in production. This milestone is to implement a set of default architecture diagrams that contain everything that's contained in the templates.
No due dateWith added features we need some more comprehensive testing. Things that currently don't have coverage include the database setup and migrations, are only tested after merges.
No due date* Set up make release-deploy command * Set up cd.yml
No due date•6/9 issues closed