boomerang-io / community

The Boomerang community, roadmap, planning, and architecture repository. The central place for information on joining, contributing, and governance.
https://useboomerang.io
Apache License 2.0
11 stars 0 forks source link

The Essential launchpad team name changed not sync to flow #325

Closed dlsyliu closed 1 year ago

dlsyliu commented 2 years ago

Describe the bug

I changed my team properties, i found after i changed the team name, it not sync to the adminster ->Quotas team name, there still display my previous team name. My old team name Admin-Quotas My new team name have been changed as below: My new team name

What project does this issue relate to?

Boomerang Flow

To Reproduce

  1. Go to flow home page https://servicesessentials.ibm.com/flow/apps/flow/workflows
  2. Click on the left navigation
  3. adminster ->Quotas
  4. Searching the team name from teams search bar will display my old team name.

Environment

prod env

Additional Contenxt

No response

tlawrie commented 2 years ago

Hi @dlsyliu thanks for this. It seems to be a very specific IBM issue. @marcusdroy @BenjaminRuby do you have any comments on this?

marcusdroy commented 2 years ago

Once essentials has created the flow team via internal apis there is currently no synchronization method to subscribe to team name updates

tlawrie commented 2 years ago

@morarucostel @gchickma over to you two to determine what's next with this or whether its closed out.

tlawrie commented 2 years ago

This should be resolved by https://github.com/boomerang-io/roadmap/issues/155

@gchickma @timrbula to confirm.

timrbula commented 2 years ago

@tlawrie Sorry don't follow here. Do the changes in 155 perform synchronization with team name updates with an external source (ie the platform?)

tlawrie commented 2 years ago

No, that's my mistake, thought it was the CICD header name not coming through.

tlawrie commented 2 years ago

Back to @gchickma

tlawrie commented 1 year ago

This won't be a problem in Flow v4 as Teams are created and managed via an API and not sync'd. Only users are sync'd.