Synk | Simple library to wrap an Async Task android class | Reactive Programming library

I tested and got the same result. It seems that the AAD group can only be retrieved by get ADO groups API after it is searched in ADO portal.

I saw you were trying adding the AAD groups to ADO groups via ADO rest api. You can use Groups - Create rest api as workaround. There is no need to get the aad group's descriptor first. You can use the Object Id of the AAD group directly.

POST:

That is a very complete scope, good work.

I would add an AMI build stage, that would build app specific AMIs using Packer. See
https://github.com/awslabs/ami-builder-packer for a good reference architecture.

I would also consider dynamic operations dashboards, that would generate a updated CloudWatch dashboard based a key/updated resources used in the project.

Consider something like semantic or conventional commit syntax, that would launch dynamic build activities based on human/machine readable tags added to commit messages

Semantic Commits are commit messages with human and machine readable meaning, which follow particular conventions

For example, if you push a commit message with the string build/preview, the build pipeline would launch a preview deployment on demand. It could take the pr number and make a dynamic url for the app that might persist until the branch is merged. https://nitayneeman.com/posts/understanding-semantic-commit-messages-using-git-and-angular/ for some ideas there.

I didn't see it called out, but unit tests, funcional tests, and api tests should be included in the dynamic application software tests.

Load tests and vulnerability tests can be performed on completed deployments, to ensure each build conforms to established performance or security standards.

Also consider in your pipeline building full infrastructure from code, if you are using Terraform or Cloudformation. Knowing that you can build everything from scratch is a great baseline. Using AWS Organizations you can even create new AWS accounts from scratch, and build your entire infrastructure in a new account.

Docker image security scanning is another important pipeline stage related to container security. Images can be scanned against CVE and other vulnerability lists. See https://docs.docker.com/engine/scan/

I like to add a documentation/report publishing stage, that take project assets and integrate them into online documentation systems. For example, you can use Antora/AsciiDoctor/Netlfy to build a documentation toolchain that would generate HTML, pdf, and Docx files for all project documentation, directly from the project repo, at build time. see https://fedoramagazine.org/using-antora-for-your-open-source-documentation/