Skip to content

Conversation

@MatthewLemmond
Copy link
Member

Description

Adds a new layer for the account infrastructure base and creates the audit, observability, and security resource groups based on what is set then passes that to the subsequent layers

NOTE:
due to existing resource group currently only being for the observability resource group in the account infrastructure base the input for existing resource group is removed, though we should be able to add the functionality to provide existing resource groups there

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@MatthewLemmond
Copy link
Member Author

/run pipeline

Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some comments. My concern is that the COS instance is getting created in the Observability group, but its being used by Event Notifications and SCC. But I might see if I can add a COS member its the stack here

"resource_group_name": $PREFIX,
"audit_resource_group_name": "{{PREFIX}}-audit",
"observability_resource_group_name": "{{PREFIX}}-observability",
"security_resource_group_name": "{{PREFIX}}-security",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what your trying to do here is not supported. However since a prefix value is added to these groups, you can just add any text in here and prefix value will ensure they are unique for every test, so they dont clash

"key": "audit_resource_group_name",
"type": "string",
"default_value": "__NULL__",
"required": true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing description

{
"key": "observability_resource_group_name",
"type": "string",
"default_value": "__NULL__",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing description

"required": true
},
{
"key": "security_resource_group_name",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing description

Copy link
Member

@vburckhardt vburckhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's park this PR for the initial release to get it right. I'd suggest to have the initial stack version deploy only to existing resource group.

"default": false,
"description": "Whether to use an existing resource group.",
"default": "us-south",
"description": "The region to deploy the Deployable Architecture",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The region in which all resources are deployed.

"outputs": [
{
"key": "audit_resource_group_name",
"description": "The Name of the audit Resource Group."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would need to follow our editorial guidelines -

something like: "The name of the resource group that is created by this solution. The actual name is prefixed with the value of the input 'prefix'. All resources created by this solution are deployed in this resource group. "

@ocofaigh
Copy link
Contributor

ocofaigh commented Apr 1, 2025

No plans to implement

@ocofaigh ocofaigh closed this Apr 1, 2025
@ocofaigh ocofaigh deleted the add-account-infra-base branch April 1, 2025 10:47
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

Successfully merging this pull request may close these issues.

4 participants