Hello,
I am encountering a duplication issue when adding Links to compass.yaml files. Whenever a new Link is added to my compass.yaml file, the Link is duplicated in the web UI.
If I then make any subsequent update to my compass.yaml, such as adding a label, I encounter the following error:
The most recent compass.yml had errors:
---
Duplicate Link in the compass_component_getComponentDetails API Response:
---
Hi, @DarrenDooley ! Thank you for reaching out.
Not sure yet what could have caused a duplicated link and the original synchronization error for the provided component, but a workaround for these situations could be a fresh re-sync with the config-as-code Compass configuration as generated by the application, which would consist of the following steps:
Looking at the logs, it looks like the most recent sync errors are due to custom fields where the option display value is sent instead of the ID? However, something like:
customFields:
- name: 'Has NewRelic Dashboard'
type: 'single_select'
displayValue: yes
Would seem okay to me.
In any case, let me know whether the generated file differs from your original configuration, and whether the fresh resync fixes it!
Quick update on this one @DarrenDooley : our team has been able to reproduce a similar condition that, under certain situations, results in the creation of duplicated links when handling a component via config-as-code. Our engineers are working on a resolution. We'll keep you posted about how this progresses!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Enrique Serrano Valle thank you for your response.
I am able to recreate this very consistently and a fresh resync of my config-as-code does not seem to resolve.
Here are the steps I performed:
1. I deleted my compass.yaml file and pushed an update to my main branch.
2. I deleted all links on my component except my repository to start fresh.
3. I copied the compass.yaml file from the config-as-code section in my component.
The Links snippet was as follows:
links:
- name: null
type: REPOSITORY
url: 'https://github.com/my-org/compass-example'
4. I pushed a new update using this fresh compass.yaml file and my compass synced correctly.
5. I added one DASHBOARD Link to my compass.yaml file:
links:
- name: null
type: REPOSITORY
url: 'https://github.com/my-org/compass-example'
- name: NewRelic
type: DASHBOARD
url: 'https://example.com/newrelic'
6. I pushed a new update and again observed duplicate links:
7. I deleted my compass.yaml file again and went to the config-as-code section in my component and there were duplicate links there too:
links:
- name: null
type: REPOSITORY
url: 'https://github.com/my-org/compass-example'
- name: NewRelic
type: DASHBOARD
url: 'https://example.com/newrelic'
- name: NewRelic
type: DASHBOARD
url: 'https://example.com/newrelic'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @DarrenDooley , after looking into this, I think this behavior is being caused by 2 Push event webhooks being received almost simultaneously. Would you be able to check your Organization and Repository webhooks in GitHub to see if there is some kind of duplication happening there?
Please also feel free to open a Support case and reference this conversation to share any information privately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @April G looks like that did the trick! We had two Atlassian webhooks configured in Github . Removing one of them fixed the problem. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@DarrenDooley that's great! Can we ask whether the duplicate webhook was manually created by someone on your team to test something? We're trying to determine whether the GitHub app may have an edge case where it could create 2 webhooks. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.