Given the point of this repo is to lower the barrier to entry for a starter Cloud Foundry deployment, the necessity of finding (amidst the ocean of AMIs in AWS) various CentOS AMIs, just so you can then go and "accept the license" is a total pain in the posterior, has nothing to do with the technology itself, and hurts the user by putting yet another barrier in their way.
Suggestion: Switch to an AMI/Stemcell that doesn't require agreeing to a license outside of the standard workflow expected from this repository.
In other words, the fact that you have to go outside your terminal to click a damn button to satisfy some insane lawyers somewhere is just plain stupid and needs to die.
Alternative: Is there a programmatic way that we can accept the CentOS license terms? And if so, can we transparently tie that in to this tool's orchestration (e.g. via HTTP request to an API end point) so that it just goes and accepts it automatically and prints out a message to the user explaining what it did, why it has to, and linking them to the legalese that probably nobody's ever going to read anyway?
Given the point of this repo is to lower the barrier to entry for a starter Cloud Foundry deployment, the necessity of finding (amidst the ocean of AMIs in AWS) various CentOS AMIs, just so you can then go and "accept the license" is a total pain in the posterior, has nothing to do with the technology itself, and hurts the user by putting yet another barrier in their way.
Suggestion: Switch to an AMI/Stemcell that doesn't require agreeing to a license outside of the standard workflow expected from this repository.
In other words, the fact that you have to go outside your terminal to click a damn button to satisfy some insane lawyers somewhere is just plain stupid and needs to die.
Alternative: Is there a programmatic way that we can accept the CentOS license terms? And if so, can we transparently tie that in to this tool's orchestration (e.g. via HTTP request to an API end point) so that it just goes and accepts it automatically and prints out a message to the user explaining what it did, why it has to, and linking them to the legalese that probably nobody's ever going to read anyway?