Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spatial data management tweaks action #2064

Closed
wants to merge 6 commits into from

Conversation

greg-does-weather
Copy link
Collaborator

What does this PR do? 🛠️

What does the reviewer need to know? 🤔

Screenshots (if appropriate): 📸

@greg-does-weather greg-does-weather force-pushed the spatial-data-management-tweaks-action branch from c93fe5c to ffc102b Compare November 7, 2024 23:47
@greg-does-weather
Copy link
Collaborator Author

The approaches from this PR won't work. I was trying to just reuse our existing script, but it depends on the Docker runner being the same machine that the cf SSH tunnel is listening on. That's fine in our local dev environments, but it breaks in GitHub where the Docker runner is a remote host.

I think a workable solution would be to create another container that hosts the cf cli and that container would establish the SSH tunnel to cloud.gov. Running that container on the same virtual network as the spatial container should solve the problem of them being able to communicate. And I think this approach is more robust anyway, making fewer assumptions about the systems external to Docker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant