rfuelsh

handled via: https://github.com/FuelLabs/fuel-core/pull/506

@ellioty - let me know if you need any help with updating the logic to trigger the workflows based on: - create eph env workflow -> if PR is created...

add logic for: 1) for .github/workflows/deploy-test-env.yml - build and create the docker image and tag it with sha - deploy eph env based on creating a PR 2) for .github/workflows/delete-test-env.yml...

TEST RESULTS: 1) Deploy Eph ENV based on branch "create-eph-envs-workflows" on PR https://github.com/FuelLabs/fuel-core/pull/506 Fuel Core Action: https://github.com/FuelLabs/fuel-core/actions/runs/2864783926 Fuel Deployment Action: https://github.com/FuelLabs/fuel-deployment/actions/runs/2864820823 % kubectl get ns NAME STATUS AGE amazon-cloudwatch Active...

the logic suggested has been implemented here is using ci.yaml to deploy to new ephemeral env using sha image tag built: https://github.com/FuelLabs/fuel-core/actions/runs/3120881863

@Voxelot - can I get a review please of this ? thanks

already handled by https://github.com/FuelLabs/fuel-core/pull/506

Need to think of better ways to setup developer environments other than bash scripts with open source tools - suggestions are Tilt, Skaffold, and others.

@xgreenx - maybe that is something @Voxelot can chime in- i don't have those github permissions to fork repos I believe

@Voxelot - would it better to investigate another action or can you assist with the forking on this action code repo? (I don't have the fork repo permissions I think)