-
Notifications
You must be signed in to change notification settings - Fork 171
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
Create an "Architecture Approach" file for the AKS Baseline presets #275
Comments
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
Picking this up again now. |
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
@MattLeach25 - We should do a metadata comparison and verify any remaining gaps. I don't think there are many/any - but would be great to verify then we can consider PR'ing guidance into the Docs/mspnp repo to link to the Baseline scenarios in AKS Construction Helper. |
The Wizard UI has been made extensible to allow for different architecture approach configuration files to be created.
Each architectural approach will contain multiple preset configurations for the AKS Environment.
It would be create to iterate on the currently disabled preset file for the AKS Baseline, to properly set up the presets for
Any gaps should be captured and proposed before beginning work in a PR for them.
The text was updated successfully, but these errors were encountered: