I'm in the process of figuring out how to have parallel production and development environments for this project.
My current thoughts are to have two sets of Lambda/Alexa project pairs, and script the deployment of SNAPSHOTs vs. releases to the appropriate place.
I believe the only part of the project that doesn't currently support this type of parallel setup is the skill-app-id. Currently we only support one of these, pulled from src/main/resources/onebusaway.properties (see setup page for details). So, I'd need to manually change this every time I switch from dev to prod, or vice versa. I'd prefer not to have to do this manually to avoid potential mistakes that could result in interrupting service.
I'd like to change this property name and add another to support production and dev environments, something like:
skill-app-id-production
skill-app-id-development
This way I'd be able to locally configure both IDs without having to resort to manually changing the config file when switching from dev to production deployments.
@philipmw Any wisdom on this topic from other skills you've deployed?
I'm in the process of figuring out how to have parallel production and development environments for this project.
My current thoughts are to have two sets of Lambda/Alexa project pairs, and script the deployment of SNAPSHOTs vs. releases to the appropriate place.
I believe the only part of the project that doesn't currently support this type of parallel setup is the
skill-app-id
. Currently we only support one of these, pulled fromsrc/main/resources/onebusaway.properties
(see setup page for details). So, I'd need to manually change this every time I switch from dev to prod, or vice versa. I'd prefer not to have to do this manually to avoid potential mistakes that could result in interrupting service.I'd like to change this property name and add another to support production and dev environments, something like:
skill-app-id-production
skill-app-id-development
This way I'd be able to locally configure both IDs without having to resort to manually changing the config file when switching from dev to production deployments.
@philipmw Any wisdom on this topic from other skills you've deployed?