Closed drewmoseley closed 6 years ago
Note that the start up script still needs to be parameterized for GCP cloud project and such.
@ptone @Kcr19 I've updated this a bit. Using only the state script to hold of server connections did not work since the Mender certificate only gets generated after that script returns. I added a systemd pre-exec script that manually creates it and is always invoked before the Mender client is actually launched. That seems to work and now the certificate is created and the mender client sits waiting for the creation of the preauth_true file.
We still need to make the project ID and such configurable.
@Kcr19 @ptone I have added some logic to make the PROJECT_ID and other GCP variables configurable. At build time they are stashed in /opt/gcp/etc/gcp-config.sh. The activation agent and sample python start script pull the data from there.
As far as I can tell, this PR is ready for review and testing through a full build/test cycle.
I think this one is ready. Any comments?
Looks good to me. Do I do PR against this branch "Autostart" for testing out ?
On Wed, Aug 15, 2018, 3:30 PM Drew Moseley notifications@github.com wrote:
I think this one is ready. Any comments?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Kcr19/mender_gcp_ota_demo/pull/10#issuecomment-413309054, or mute the thread https://github.com/notifications/unsubscribe-auth/AVs9HfKw8ZvhjE6ubMFFEB-5HY9Fcpveks5uRHbTgaJpZM4V3Pqh .
You should not need another PR for testing. If you manually download the build script and modify it to checkout from my fork and branch instead of yours, that should suffice for testing. The alternative is to simply merge this and then fix any issues in subsequent commits.
This is not yet ready for merge but it is ready to be reviewed.