Bug Report: Something was preventing the IFederatedLogin to appears in the `Deploy Plan`.

[felipe-beamable]

this happened on main

---

We created a new microservice called BeamFarmMs on dev, this microservice was empty ( No Method Wrote ), but was published and was running by looking in the portal.

I added the IFederatedLogin, but it wasn't been published to portal.

• The Federation didn't appears in the Plan.json.
• The Federation could be found on the open api.
• When I started the MS locally it was possible to see in the logs the federation running.

OBS: Don't know if it's related but it just start to work when I check again after restart my computer.

[cdhanna]

the plan command uses the oapi spec file to decide if there are federations... So if the file says there are federations, but the plan command does not, then there is a bug in the plan's logically handling of the data.

Or, it could be possible that the file was missing the data the first time.

[cdhanna]

Re-run some repro steps,

1. create a brand new beamable workspace,
2. create a new service
3. DO NOT BUILD IT YET
4. add a federation
5. jump straight to deploy plan
6. Expect to see federation in plan, but actually see it is not there :(

[DiasAtBeamable]

Did some testing and I could not reproduce it. I'm using my local Beam version.

I'm going to try using the latest CLI available to see if it happens too.

[DiasAtBeamable]

It also worked just fine in CLI 6.2.2.

[DiasAtBeamable]

Closing it as a no-repro.