Skip to content

Conversation

@iamar7
Copy link
Member

@iamar7 iamar7 commented Jun 10, 2025

Description

Add Metrics Router Account Settings variation

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.

@iamar7 iamar7 marked this pull request as ready for review July 8, 2025 13:35
@iamar7 iamar7 requested a review from shemau as a code owner July 8, 2025 13:35
@iamar7
Copy link
Member Author

iamar7 commented Jul 8, 2025

/run pipeline

@arya-girish-k
Copy link
Contributor

/run pipeline

Copy link
Contributor

@shemau shemau left a comment

Choose a reason for hiding this comment

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

I am failing to understand why this is a different DA and not included in the fully configurable DA. There seem to be routes, targets and settings. Why are only routes and targets set up in one, and only settings in the other. All three resources seem to be conceptually linked.

I am not sure if this is the right question, but why doesn't fully configurable, as the name suggests duplicate this function? Was the plan to add this at the project level later (dependancies, add-ons etc)?

@arya-girish-k
Copy link
Contributor

I am failing to understand why this is a different DA and not included in the fully configurable DA. There seem to be routes, targets and settings. Why are only routes and targets set up in one, and only settings in the other. All three resources seem to be conceptually linked.

I am not sure if this is the right question, but why doesn't fully configurable, as the name suggests duplicate this function? Was the plan to add this at the project level later (dependancies, add-ons etc)?

@shemau :This is a request from observability team .Please find the discussion and the related issue for your reference.

@arya-girish-k
Copy link
Contributor

/run pipeline

@arya-girish-k
Copy link
Contributor

/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.

see comments

@arya-girish-k
Copy link
Contributor

/run pipeline

@arya-girish-k
Copy link
Contributor

/run pipeline

@arya-girish-k
Copy link
Contributor

/run pipeline

@arya-girish-k arya-girish-k requested a review from ocofaigh July 17, 2025 09:34
@arya-girish-k
Copy link
Contributor

/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.

final few comments

@arya-girish-k
Copy link
Contributor

/run pipeline

@arya-girish-k
Copy link
Contributor

/run pipeline

@vkuma17
Copy link

vkuma17 commented Jul 21, 2025

/run pipeline

@ocofaigh
Copy link
Contributor

ocofaigh commented Jul 21, 2025

@arya-girish-k We will keep seeing this error due to tests conflicting with each other. It is probably safe to add this to the ignore update list in the test so we don't have regular conflicting tests:

       	Messages:   	Resource(s) identified to be updated 
        	            	Name: metrics_router_settings
        	            	Address: module.metrics_routing[0].ibm_metrics_router_settings.metrics_router_settings[0]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"primary_metadata_region":"eu-de"}
        	            	  After: 
        	            		{"primary_metadata_region":"eu-fr2"}

@arya-girish-k
Copy link
Contributor

/run pipeline

@arya-girish-k
Copy link
Contributor

@arya-girish-k We will keep seeing this error due to tests conflicting with each other. It is probably safe to add this to the ignore update list in the test so we don't have regular conflicting tests:

       	Messages:   	Resource(s) identified to be updated 
        	            	Name: metrics_router_settings
        	            	Address: module.metrics_routing[0].ibm_metrics_router_settings.metrics_router_settings[0]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"primary_metadata_region":"eu-de"}
        	            	  After: 
        	            		{"primary_metadata_region":"eu-fr2"}

Added ignoreupdate list in the test

@arya-girish-k arya-girish-k requested a review from ocofaigh July 21, 2025 18:44
@arya-girish-k
Copy link
Contributor

/run pipeline

@ocofaigh ocofaigh merged commit 1ae9c7a into main Jul 22, 2025
2 checks passed
@ocofaigh ocofaigh deleted the 13686-acc branch July 22, 2025 10:22
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 1.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

TemplateFolder: AccountSettingsDADir,
Tags: []string{"mr-da-test"},
DeleteWorkspaceOnFail: false,
WaitJobCompleteMinutes: 60,
Copy link
Contributor

Choose a reason for hiding this comment

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

@arya-girish-k I just noticed you never added the IgnoreUpdates here - I suspect this will eventually fail due to same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants