I am testing this module against a new empty site.

There are 3 sites: dev, test and prod.
Each site has a single Live workspace. Stage was removed.
Each site has a remote to the other 2.

The Status Report is totally fine, and there are no related errors in the log.

The sites were created by copying a working site and creating the other 2 environments.

I have 3 issues:
1. When I try to create or edit a Workspace, the only option I have is the Dev environment.
This means that Dev can only see its own Workspaces, and Test and Prod only see Dev.
Workaround: Editing and saving a remote seems to trigger an awareness in the other sites, but it shouldn't have to work this way.

2. Even though none of the sites have a Stage environment, I still see 2 workspace options for each remote: Life and Stage.

3. For the purposes of easy import/export and development workflow, each site is aware of all 3 sites. This means that I could configure a workspace to talk to its own remote and workspace. It would be nice to have "self" excluded when selecting a workspace.

I reported these together because they might be caused by a single refresh issue, which I don't fully understand.

Thanks for the great module!!!

Comments

arnaldop created an issue.

jeqq’s picture

jeqq commented

Thanks @arnaldop for reporting this!

1. I don't think I understand what was the issue here. Maybe you mean the new remote workspaces don't appear on the sites that point to the remote the new workspace belongs to - in this case cron should be run, new workspace pointers for new remote workspaces are added after cron run.

2. I've created an issue for this: #3023600: Delete the workspace pointer for the deleted remote workspaces on cron run

3. I understand your point here, but I don't think it's high a priority problem, for now.