As a tester using galasa, I want to point my GALASA_BOOTSTRAP environment variable at an ecosystem, and
have the ability to run a local test which uses the CPS store from the remote ecosystem, as it's simpler than setting 2 magical parameters into my local bootstrap.properties file and referring to that.
Background
To get the remote CPS used by the local ecosystem, you currently set these properties into your local bootstrap.properties file:
The /bootstrap URL of any ecosystem doesn't currently return any properties.
We want it to return those properties, so that the only thing you need to do to run a local test is set the GALASA_BOOTSTRAP environment variable to refer to your local ecosysyem, and set GALASA_TOKEN properly, then you can get this hybrid behaviour with less configuration.
Story
As a tester using galasa, I want to point my GALASA_BOOTSTRAP environment variable at an ecosystem, and have the ability to run a local test which uses the CPS store from the remote ecosystem, as it's simpler than setting 2 magical parameters into my local bootstrap.properties file and referring to that.
Background
To get the remote CPS used by the local ecosystem, you currently set these properties into your local
bootstrap.properties
file:The /bootstrap URL of any ecosystem doesn't currently return any properties.
We want it to return those properties, so that the only thing you need to do to run a local test is set the GALASA_BOOTSTRAP environment variable to refer to your local ecosysyem, and set GALASA_TOKEN properly, then you can get this hybrid behaviour with less configuration.
This work is related to #1813
Tasks