Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do i add encrypted files or env variables to the build process? #16

Open
frozeman opened this issue Jan 14, 2020 · 4 comments
Open
Labels
enhancement New feature or request question Further information is requested

Comments

@frozeman
Copy link

I followed the tutorial here, but using this package I couldn't add the cloudbuild.yml anywhere, as it doesn't use the root folder to deploy, but the bundle folder. How could it add the decrypt steps without forking your package?

@iamstevendao
Copy link
Contributor

@frozeman You can use option --build-only, which will build the project into output/bundle folder, then you can deploy from there.

@frozeman
Copy link
Author

frozeman commented Jan 16, 2020

i see thanks.

So simply

$ ... --build-only
$ cd output/bundle
$ gcloud submit ....

But it would be nice to be able to simply add google cloud build steps to decode ENV or files while submitting.

@iamstevendao
Copy link
Contributor

@frozeman Yep, it would be nice. For now, if you used cloud build steps to decrypt the files, meteor-google-cloud would be used for the build step only.

@raphaelarias
Copy link

I tend to believe the package should take care of the build and deploy only. If we add decryption of variables it may start to increase the scope too much. I'm not sure.

@raphaelarias raphaelarias added enhancement New feature or request question Further information is requested labels Jan 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants